Non-PMC members can certainly make releases. I would suggest at
present just clarify step 15 to say "update, or ask for someone to
update".
The board report is in a private area on the off chance that something
non-public needs to be included. However such a thing would need to be
appropriately marked, so perhaps we could move them in public and
handle any (rare) additions privately.
Or at least move the release list somewhere public and paste it into
the report.
Thanks for going through these steps!
Cheers,
Brett
On 12/10/2008, at 11:08 AM, Vincent Siveton wrote:
2008/10/11 Barrie Treloar <[EMAIL PROTECTED]>:
On Sun, Oct 12, 2008 at 10:27 AM, Vincent Siveton
<[EMAIL PROTECTED]> wrote:
I am saying that the PMC should take care of all releases (PMC or
not), and then update this file.
Hope that it is clear.
Ok,
I don't care either way, but developers/release/releasing.html needs
to be updated to indicate PMC use only.
+1 to update it.
Vincent
I assume Jason as V.P., Apache Maven is the one to decide the
process?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
