You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by Joe Schaefer <jo...@yahoo.com> on 2009/01/12 16:05:50 UTC
Re: svn commit: r733711 - /httpd/apreq/branches/1.x/RELEASE
----- Original Message ----
> From: "issac@apache.org" <is...@apache.org>
> To: apreq-cvs@httpd.apache.org
> Sent: Monday, January 12, 2009 7:49:45 AM
> Subject: svn commit: r733711 - /httpd/apreq/branches/1.x/RELEASE
>
> Author: issac
> Date: Mon Jan 12 04:49:42 2009
> New Revision: 733711
>
> URL: http://svn.apache.org/viewvc?rev=733711&view=rev
> Log:
> update the release cycle instructions
>
> Modified:
> httpd/apreq/branches/1.x/RELEASE
>
> Modified: httpd/apreq/branches/1.x/RELEASE
> URL:
> http://svn.apache.org/viewvc/httpd/apreq/branches/1.x/RELEASE?rev=733711&r1=733710&r2=733711&view=diff
> ==============================================================================
> --- httpd/apreq/branches/1.x/RELEASE (original)
> +++ httpd/apreq/branches/1.x/RELEASE Mon Jan 12 04:49:42 2009
> @@ -16,7 +16,7 @@
> 3. Upload a release candidate to httpd.apache.org/~username
> and post a candidate announcement to apreq-dev@. The RM
> or any other apreq committer may call for a formal vote on the
> - candidate, but a formal vote is not a requirement for the release.
> + candidate, but a formal vote is not a requirement for the candidate.
> Also, it is strongly recommended that the RM crosspost the
> candidate announcement to the modperl@ list, to solicit feedback
> from a much larger audience.
This section is totally wrong. Formal votes on releases
is a foundation-wide requirement, and crossposting the candidate
announcement to the modperl@ list is effectively releasing
the candidate, so it should not be done.
> @@ -36,6 +36,10 @@
> =item 1.35 -
>
> libapreq-1.35 released.
> +
> + Also, add a release entry to ./STATUS
> +
> + 1.35 : Released
>
> 6. Tag the tree, s/./_/g in the version number, and roll the release.
>
> @@ -82,21 +86,40 @@
> /www/www.apache.org/dist/httpd/KEYS file.
> ---------------------------------------------------
>
> -9. Upload the package to CPAN. Doublecheck that the md5 checksum
> - received from PAUSE is correct.
> +9. Call for a formal vote on the release artifact as explained in 4 and 5
> + above. Note that since this is a release artiface, a formal vote is
> + required, and 3 +1 votes from members of the httpd PMC are required to
> + proceed. If all is well after 72 hours, proceed to step 11 (NOT 10).
We shouldn't bless what was done with 1.34, as stuff should never be put
on the mirror system (www.apache.org/dist/) until AFTER it has passed a vote.
Re: svn commit: r733711 - /httpd/apreq/branches/1.x/RELEASE
Posted by Issac Goldstand <ma...@beamartyr.net>.
Joe Schaefer wrote:
> ----- Original Message ----
>
>
>> From: "issac@apache.org" <is...@apache.org>
>> To: apreq-cvs@httpd.apache.org
>> Sent: Monday, January 12, 2009 7:49:45 AM
>> Subject: svn commit: r733711 - /httpd/apreq/branches/1.x/RELEASE
>>
>> Author: issac
>> Date: Mon Jan 12 04:49:42 2009
>> New Revision: 733711
>>
>> URL: http://svn.apache.org/viewvc?rev=733711&view=rev
>> Log:
>> update the release cycle instructions
>>
>> Modified:
>> httpd/apreq/branches/1.x/RELEASE
>>
>> Modified: httpd/apreq/branches/1.x/RELEASE
>> URL:
>> http://svn.apache.org/viewvc/httpd/apreq/branches/1.x/RELEASE?rev=733711&r1=733710&r2=733711&view=diff
>> ==============================================================================
>> --- httpd/apreq/branches/1.x/RELEASE (original)
>> +++ httpd/apreq/branches/1.x/RELEASE Mon Jan 12 04:49:42 2009
>> @@ -16,7 +16,7 @@
>> 3. Upload a release candidate to httpd.apache.org/~username
>> and post a candidate announcement to apreq-dev@. The RM
>> or any other apreq committer may call for a formal vote on the
>> - candidate, but a formal vote is not a requirement for the release.
>> + candidate, but a formal vote is not a requirement for the candidate.
>> Also, it is strongly recommended that the RM crosspost the
>> candidate announcement to the modperl@ list, to solicit feedback
>> from a much larger audience.
>>
>
> This section is totally wrong. Formal votes on releases
> is a foundation-wide requirement, and crossposting the candidate
> announcement to the modperl@ list is effectively releasing
> the candidate, so it should not be done.
>
>
But this isn't a release, it's a candidate and will never be blessed by
the ASF in any manner. I'd suggest leaving the vote instructions as-is
(they're technically correct) and removing the crosspost until the
actual release. Sound ok?
>
>> @@ -36,6 +36,10 @@
>> =item 1.35 -
>>
>> libapreq-1.35 released.
>> +
>> + Also, add a release entry to ./STATUS
>> +
>> + 1.35 : Released
>>
>> 6. Tag the tree, s/./_/g in the version number, and roll the release.
>>
>> @@ -82,21 +86,40 @@
>> /www/www.apache.org/dist/httpd/KEYS file.
>> ---------------------------------------------------
>>
>> -9. Upload the package to CPAN. Doublecheck that the md5 checksum
>> - received from PAUSE is correct.
>> +9. Call for a formal vote on the release artifact as explained in 4 and 5
>> + above. Note that since this is a release artiface, a formal vote is
>> + required, and 3 +1 votes from members of the httpd PMC are required to
>> + proceed. If all is well after 72 hours, proceed to step 11 (NOT 10).
>>
>
> We shouldn't bless what was done with 1.34, as stuff should never be put
> on the mirror system (www.apache.org/dist/) until AFTER it has passed a vote.
>
Good point. I knew that but missed fixing it.