The release manager is not necessary a PMC member, bit he/she has to be a committer of the project.

See: http://www.apache.org/dev/release-publishing.html#release_manager


On 5/5/19 12:26 AM, Geertjan Wielenga wrote:
Is it a requirement that the volunteer release manager is a PMC
member/committer? Or does it make it easier, or does it not make
a difference?

Gj

On Sat, May 4, 2019 at 4:48 PM Laszlo Kishalmi <[email protected]>
wrote:

The main responsibilities are: herding people, PR-s, JIRA issues towards
the goal of forming a healthy release.

Some other useful reading:

   * https://www.apache.org/dev/release-publishing.html
   * https://www.apache.org/dev/release-distribution.html
   * https://www.apache.org/legal/release-policy.html
   *
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README
   * https://issues.apache.org/jira/browse/NETBEANS-2052
   * https://issues.apache.org/jira/browse/NETBEANS-1321

On 5/3/19 11:22 PM, Vano Beridze wrote:

Hello,

What are the responsibilities?

Vano

On Sat, May 4, 2019, 10:10 AM Laszlo Kishalmi <[email protected]

wrote:

Dear all,

I've sent this one earlier, maybe too early, though there was not a
single response to this.

Probably we shall agree on how would we imagine the 11.1 release. For me
the theme would be:

    * Bugfixes
    * Java EE 8 Support
    * Java EE Support for Gradle

Of course we can do something else, like just do a few module updates,
or completely opt out for 11.1...


I know that 11.0 is just has been pushed out the door, but if we would
like to do a NetBeans 11.1 in June we need someone who takes the reins.
We need a release schedule, the way of work (branching, JIRA, etc.)
soon.
I've already taken this position twice, it has been quite a journey,
thank you!

Beside the usual RM stuff which we did do far I see the following new
challenges:

   1. This is a minor release, probably coordinating changes would be a
      bit easier.
      I guess we'd just branch off release110 to release111 and continue
      to cherry-picking from master.
   2. This would be the first release as Apache top level project
   3. Probably we need to experiment releasing patches, or release 11.1
as
      a set of parches...
   4. Codes for 12.0 will be run in parallel on master, so JIRA tracking
      could be a bit harder.

As of myself, I'd concentrating on development and bug-fixing in the
next couple of cycles.

So think about it!

Volunteers we Need you!

Laszlo Kishalmi

Former Release Manager of Apache NetBeans



---------------------------------------------------------------------
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



Reply via email to