Submariner organizes all current and upcoming work using GitHub Issues, Projects, and Milestones.
In preparation for sprint planning meetings (see Submariner’s Community Calendar), GitHub Issues should be raised for work that is to be a part of a sprint. Issues targeted for a sprint should be added to the upcoming Project’s “Backlog” column. During sprint planning meetings, Issues will be discussed and moved to the “TODO” column and the milestone will be set to the targeted release. As contributors make progress during sprints, Issues should be moved through the “In Progress”/“Review/Verify”/“Done” columns of the Project. If an Issue is implemented during a release but additional work (like an ACK-fixed verification) tracked by the relevant Issue is necessary, the Issue can be carried over to the next Project but the Milestone should reflect where the code was shipped for accurate release note creation.
Current and near-future work is tracked by Submariner’s open Projects.
Some high-level goals are summarized here, but the primary source for tracking future work are Submariner’s GitHub Issues.
If we are missing something that would make Submariner more useful to you, please let us know. The best way is to file an Issue and include information on how you intend to use Submariner with that feature.