Re: simplify release procedure

2016-10-31 Thread Robert Scholte
Yes, it's PMC only, uploading those files or updating the board-report too. Robert On Mon, 31 Oct 2016 18:52:53 +0100, Hervé BOUTEMY wrote: AFAIK, this site is available only to PMC members: this won't change the karma required, just avoid to do the job twice -- which is already something

Re: simplify release procedure

2016-10-31 Thread Hervé BOUTEMY
AFAIK, this site is available only to PMC members: this won't change the karma required, just avoid to do the job twice -- which is already something useful :) Regards, Hervé Le lundi 31 octobre 2016, 18:41:00 CET Robert Scholte a écrit : > Extending chapter "Copy the source release to the Apa

Re: simplify release procedure

2016-10-31 Thread Robert Scholte
Extending chapter "Copy the source release to the Apache Distribution Area" "After committing the 3 source-release files, visit https://reporter.apache.org/addrelease.html?maven to add your release data with the Full Version Name and Date of Release. (You will receive an e-mail for it as we

Re: simplify release procedure

2016-10-30 Thread Stephen Connolly
+1 to the principle. Can we see your proposed procedure (if you are tweaking one of the other steps to mention this requirement) On Sunday 30 October 2016, Robert Scholte wrote: > Hi, > > I'd like to remove step 6 of our release procedure[1]: > 6. Add the release to the next board report

simplify release procedure

2016-10-30 Thread Robert Scholte
Hi, I'd like to remove step 6 of our release procedure[1]: 6. Add the release to the next board report, in the private subversion area. This is a PMC activity. If you are not a PMC member then email the Developer's list with a request to update this file for your release. When copying the