RFC: Reorganizing the issues --> PR flow for subsequent release of gluster-colonizer #24
Description
For the next upcoming release of gluster-colonizer, I have a few suggestions and putting them out here for comments.
-
it would be good to use the "Projects" construct available to create a release number
-
each of the features which make up the release will be an issue under the respective swimlane
-
only when all the issues have been closed; because the PRs associated with them have been merged into a release branch, will the full release build be available
I propose this structure to ensure that a release is built through a series of PRs which address specific issues (which could be features or, bugs). A release has the full set of fixes and thus is ready to undergo testing prior to general availability. Any interim release, if at all, will have to be built per-PR or, similar so that, if required, a snap/interim build will contain all the PRs prior to that. A snap/interim is not a full release. Adoption of this or, a variant of this will also ensure that packaging guidelines are easily adhered to and it would facilitate tracking/auditing of all the content in a particular release.