![]() Step 3 - Create the Release Branch and Increment Metron versionĬreate an branch for the release (from a repo cloned from ). On the release date the release manager should message the Metron dev board ( announcing the code freeze for the release. The release manager should continue to monitor the JIRA to ensure that the timetable is on track until the release date. All pull requests and JIRAs that were not slated for this release will go into the next releases. Once the community votes for additional JIRAs they want included in the release verify that the pull requests are in before the release, close these JIRAs and tag them with the release name. Users should rate them as must/need/good to have as well as volunteering.Ī release email template is provided here. A solicitation of JIRAs that should be included with the next release.(See "CHANGES file" below for a grep command that will generate the list of JIRAs already committed.).The list of JIRAs slated for the release with descriptions (use the output of git log and remove all the JIRAs from the last release’s changelog).Construct an email to the Metron dev board ( discusses with the community the desire to do a release.Make sure that the list of JIRAs slated for the release accurately reflects to reflects the pull requests that are currently in master.Prior to the release The Release manager should do the following (preferably a month before the release): Creating a Feature Release Step 1 - Initiate a discuss thread All new features will be checked in under the FR branch. All patches to the previous Metron release will be checked in under the MR branch and where it makes sense also under the FR branch. notation to signify that the project is still under active development and we will hold a community vote to go to 1.x at a future time Initiating a New Metron ReleaseĬreate the MR branch for the previous Metron release by incrementing the *third* digit of the previous release like so 0. ![]() ![]() Metron build naming convention is as follows: 0. Maintenance Release (MR) - this is a set of patches and fixes that are issued following the FR and is denoted by an upgrade of the third digit.Feature Release (FR) - this is a release that has a significant step forward in feature capability and is denoted by an upgrade of the second digit. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |