Master branches will be frozen until QE signs off.Freeze starts on Wednesday night (tomorrow!) and ends on Tuesday next week after Pavol sends the email to devtools-program <email@example.com> and jbosstools-dev <firstname.lastname@example.org
g>.Subject will be something like this:"QE Approval for JBT 4.5.0.Final release - master branch is unfrozen"During the freeze, you can work on docs, N&N, JIRA triage and prepare for the future. You can also prepare PRs in topic branches.But please don't merge anything into master branch during the freeze, as it will likely NOT be included in the release (but will be included in the tag, which is confusing).HTH,NickOn Mon, Jul 31, 2017 at 4:17 AM, Aurélien Pupier <email@example.com> wrote:Hello Nick,Does it mean that the master branch will be "frozen" until the release? or we will update the master to next version and can continue to work normally?On Fri, Jul 28, 2017 at 5:03 PM, Nick Boldt <firstname.lastname@example.org> wrote:______________________________In the past, we've created a side branch as part of the code freeze for GA, (eg., 4.4.0.x, 4.4.1.x, 4.4.2.x) with the intent to be able to more easily fix a blocker during the period between the GA build (last Thurs of the GA sprint) and the GA announcement date.
But as we've seen from the last several GA releases, no blockers are found because QE is testing so much, so early, that by the time we get to the GA sprint, all the blockers have been found & fixed weeks earlier.
Therefore, while we will continue to TAG as part of every milestone release, we won't be creating a 4.5.0.x BRANCH next week on Aug 2 as part of the code freeze & stage for QE.
If you have any concerns with this plan, please voice them before August 2.--
jbosstools-dev mailing list