That's great news Neil, please drop a mail on the "Volunteer Release
Manager(s) Needed for Apache NetBeans 11.1"
thread as well, just in order to be clear on that with the others.
On 5/5/19 9:50 AM, Neil C Smith wrote:
Hi,
On Sun, 5 May 2019 at 16:32, Geertjan Wielenga <geert...@apache.org> wrote:
Regardless of who becomes the next release manager, can we get an easy view
into which pull requests will be part of the release?
IMO, if we're doing this June release we should be freezing master at
the end of May and releasing whatever is there as NB12. And fixing
that date as soon as possible so there's an advertised time to fix up
any desired PR's for that release. Cherry-picking things to include,
or deciding now whether it counts as "major" or "minor", seems counter
to doing time-based releases.
And I still think it would be good to freeze master at branch point
for anything other than fixes intended for the next release, and run
merge windows for new features after the releases are done.
I'd be happy to consider being release manager this time around, as
discussed last time, if we do something along these lines. I'm not so
keen to release manage with further cherry picking on to the
release110 branch. If it's purely about bug fixes / improvements on
select modules, can't they be done separately via the update centre?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
