On Tue, 21 Sept 2021 at 18:50, Geertjan Wielenga <[email protected]> wrote: > 1. *Release teams.* This is an idea by Neil -- let's have for each release > a team of about 5 or 6 people focused on doing specific things, e.g., let's > have at least two release managers, ... 4. 12.6 feature freeze is less than a > month away. Who'd like to be > release manager/s for this release
The idea you mention in 1. and the question in 4. are somewhat mutually exclusive. My idea was to *replace* the release manager role with an ongoing group who take on the shepherding role and understand the release processes / infrastructure. This will need to mostly be PMC members, as currently the release manager has to be a PMC member, but could include others as not all jobs need permissions. I also suggested it with almost the opposite viewpoint of people focusing on specific things. I had to withdraw through much of 12.4 due to other commitments, Eric had issues with internet access(?) for a period during 12.5 - life happens! If we have a small team, anyone can step up if they're free to do a task that needs doing on any day, without feeling like we're stepping on toes in doing so, etc. And we set up something whereby the group can keep in sync through the release process. Possibly an alternative mailing list here - there's a lot of release specific conversation that should come through ASF somehow, but is probably too high noise for dev@. > 2. *The next major release.* My proposal here is simple -- we should do > Apache NetBeans 13 whenever we have incorporated nb-javac (which we can now > legally do) completely into Apache NetBeans, not as a confusing module that > needs to be installed somewhere after startup. That will be the point where > we are fully mature and independent as a project without weirdness. From 13 > onwards, maybe each release should be a major release, i.e., there are > enough numbers in the world, we don't need minor releases anymore after > that breakpoint. +1 to the version changing and possibly dropping the idea of LTS with it. The other criteria for incrementing to 13 that has been discussed previously involved dropping JDK 8 support now that JDK 17 is out. > Thanks, other comments and thoughts welcome. The big one for me, and I think seemed to be more of an issue at start of 12.5. Sticking rigidly to the advertised freeze and branching date. We agreed a while ago to snapshot and release master from particular dates. In my opinion, that means that the default position for all unmerged / unready PRs is to move them to the next milestone. Then conversations can happen to rebase on delivery if any need to be included in the release. That way, we're not only in a better position to get betas ready on time, but we're not holding up the merging of PRs into master for the next release at the same time. We're losing some of the benefits of Laszlo's delivery branch idea. 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
