Thank you Neil!
I think we shall revisit this code freeze on master process. this time
the freeze period was about 50 days that's more than the half of a
release timeline. If the freeze would take 1-2 occasionally 3 weeks that
could be Ok. We are having advanced version control tools in our hand,
let's use them. In order to prove my point, I'd volunteer being the RM
for 12.2.
There would be a feature freeze, but after the cut of the release branch
ad do the module version update, the master branch would be free for
merge. The PR-s patching the upcoming release will have a corresponding
PR for the master (or vice-versa). So yes there would be an overhead of
maintaining PR-s for two branches for a while, but at least it would
allow code be integrated and tested on master much longer.
On 9/6/20 7:01 AM, Neil C Smith wrote:
Hi All,
Sorry for the slight delay on this following the release vote. Sig
test and spec version commits have been made.
We can now reopen master for development towards 12.2. Freeze date
for 12.2 is scheduled for Oct 15th.
Thanks and best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
