Hi all,

Here are a few observations/ideas, based on the last few releases:

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, Eric did a really great job, in general
even greater would be two people (e.g., Neil and me) to keep in sync and
call each other once a week around the release, plus a few people to create
binaries (e.g., John McDonnell who does the Mac OS X installer), as well as
a few others (e.g., Ömer Halit Çizmeci did great work on documentation) and
a few testers dedicated to the release, e.g., one or two per operating
system. If we like this idea, who'd like to be on the 12.6 release team?
Speak up. :-)

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.

3. *Release README.* We need to update the post release steps here, i.e.,
this document is gold and needs to be constantly up to date.

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README

4. *12.6 feature freeze is less than a month away.* Who'd like to be
release manager/s for this release and, see above, who'd like to be on the
release team? In whatever capacity, Neil and myself will be on that team as
well, see the schedule below:

https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule

Thanks, other comments and thoughts welcome.

Gj

Reply via email to