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 <nboldt@redhat.com> 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. 

--

Nick Boldt

Senior Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com


_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev



--

AURÉLIEN PUPIER

SENIOR SOFTWARE ENGINEER, FUSE TOOLING

Red Hat France

apupier@redhat.com    IM: apupier