On Sun, 6 Sep 2020 at 20:22, Laszlo Kishalmi <[email protected]> wrote: > 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. > ... 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.
I agree freeze was too long here, and was going to post similar. But I don't think getting rid of the freeze is the answer. We had things that didn't make the freeze date (like nb-javac) and things were a bit slower to address because I think August might not be a good month for releasing with people away / less engaged. I think we need to be much stricter about freeze dates and getting things in master much earlier. I'm -1 to just getting rid of freeze though - we had issues before with conflicting or missing fixes between master and release branches. What we have now is effectively always releasing off master, and personally I think that's the better approach. That's not to ignore more advanced version control. I think we need to get better as well at using other (feature, cluster, next) branches - PHP development seems to have been going on quite happily through freeze. Master freezing doesn't need to mean that development comes to a halt. But having the new things merge on top of the release is a positive IMO. Thanks for volunteering for 12.2! 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
