Hi all,
Thanks, Laszlo, for this great work.
Regarding the release process [1], I think we could change steps 24 and 25.
What we have now:
24. Update the WebSite for the new Release
25. Send out release announcement-s
The proposal:
24. Prepare a PR with the website for the new Release and some
screenshots for Twitter.
25. Publish the website, send out release announcements to mailing lists
and post to Twitter/elsewhere.
In step 25 we could coordinate to send announcements to mailing lists,
update the website and make some noise in Twitter and elsewhere. This is
something that involves many people, and we could coordinate in advance.
For instance, by sending an email to the mailing lists 24h in advance
(something like "we'll announce the new release on monday at 12:00 UTC").
Kind regards and thanks again,
Antonio
[1]
I love this process as documented at:
https://issues.apache.org/jira/browse/NETBEANS-2052
El 5/4/19 a las 13:22, Laszlo Kishalmi escribió:
Dear all,
I would like to thank you to be able to be the Release Manager of Apache
NetBeans 11.0!
Thank you all, who contributed in this release either by code,
documentation, advice, or shared opinion!
This cycle started a bit sleepy, either due to the new year's duties or
due to the exhaustion from over-carrying the 10.0 release. After we were
over the shock everything started to shape up nicely by end of February.
As a release manager I found it a good practice not to do a release to
staging for every vote candidate we made and we could use the artifacts
from Jenkins directly. I still hope that it did not cause any trouble
for the Apache Infrastructure. I'd keep that for the future releases as
well.
I'm still not fond of the vote candidate name. The release actually
matured nicely vc1 - alpha, vc2 - beta 1, vc3- beta 2 and vc4 is an rc1
quality. If I were not traveling through the world just at the end of
our cycle, I would have cut a vc5 as well to address the minor
non-technical concerns were found out during the voting cycle.
Some Numbers:
In this release we were resolving ~64 issues. 38 bugs, 13 improvement,
13 tasks
The release process right now consists of ~30 steps (two steps more than
10.0), about the half of these steps requires changes in the release
branch. This sets our limit to about four releases in a year, which is
not bad, but we have that limit.
I hope, I was documenting our work well enough, to make the job of the
next Release Manager easier.
This was a though, but wonderful journey! Thank you everyone for their
work and support!
Laszlo Kishalmi
Volunteer Release Manager of Apache NetBeans 11.0
P.S.: Constructive feedback on the process and on my work are , as
always, welcome!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
