[jbosstools-dev] ACTION REQUIRED: Prep for 4.5.0.Final / 11.0.0.GA - no .x branch to be created during code freeze

[Aurélien Pupier]

Hello,

Thanks for clarification
I created a Task to get rid of this long code freeze:
https://issues.jboss.org/browse/JBIDE-24789
I hope that we will be able to smooth the process

regards,

On Tue, Aug 1, 2017 at 6:00 PM, Nick Boldt <nboldt at redhat.com> wrote:

> 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 <
> devtools-program at redhat.com> and jbosstools-dev <
> jbosstools-dev at lists.jboss.org>.
>
> 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,
>
> Nick
>
> On Mon, Jul 31, 2017 at 4:17 AM, Aurélien Pupier <apupier at redhat.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 <nboldt at 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
>>> <https://red.ht/sig>
>>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>>> @ @redhatnews <https://twitter.com/redhatnews>      Red Hat
>>> <https://www.facebook.com/RedHatInc>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>>
>>
>> --
>>
>> AURÉLIEN PUPIER
>>
>> SENIOR SOFTWARE ENGINEER, FUSE TOOLING
>>
>> Red Hat France <https://www.redhat.com/>
>>
>> apupier at redhat.com    IM: apupier
>> <https://red.ht/sig>
>>
>
>
>
> --
>
> Nick Boldt
>
> Senior Software Engineer, RHCSA
>
> Productization Lead :: JBoss Tools & Dev Studio
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> @ @redhatnews <https://twitter.com/redhatnews>      Red Hat
> <https://www.facebook.com/RedHatInc>
>



-- 

AURÉLIEN PUPIER

SENIOR SOFTWARE ENGINEER, FUSE TOOLING

Red Hat France <https://www.redhat.com/>

apupier at redhat.com    IM: apupier
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20170802/ad79fe3e/attachment-0001.html