You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Hyrum K. Wright" <hy...@mail.utexas.edu> on 2010/07/13 16:03:21 UTC
Re: svn commit: r963767 - /subversion/site/publish/docs/community-guide/releasing.part.html
Bonus points if somebody writes a script to do all this website update
release magic for us.
On Tue, Jul 13, 2010 at 4:53 PM, <cm...@apache.org> wrote:
> Author: cmpilato
> Date: Tue Jul 13 15:53:32 2010
> New Revision: 963767
>
> URL: http://svn.apache.org/viewvc?rev=963767&view=rev
> Log:
> * site/publish/docs/community-guide/releasing.part.html
> (releasing-release): Update the website tweaking instructions, and
> add a reminder to update our published API doc snapshots as part of
> the release process, too.
>
> Modified:
> subversion/site/publish/docs/community-guide/releasing.part.html
>
> Modified: subversion/site/publish/docs/community-guide/releasing.part.html
> URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=963767&r1=963766&r2=963767&view=diff
> ==============================================================================
> --- subversion/site/publish/docs/community-guide/releasing.part.html (original)
> +++ subversion/site/publish/docs/community-guide/releasing.part.html Tue Jul 13 15:53:32 2010
> @@ -1062,14 +1062,19 @@ freshmeat crew before it goes public.</p
>
> <p><b>Update the website</b></p>
> <ol>
> - <li>Edit the www/project_status.html file appropriately in /trunk
> - *NOT* in the release branch and commit. Remember edit a search term
> - at the end of release's issue link.</li>
> - <li>Update the best available version on the front page and at the
> - top of www/getting.html</li>
> - <li>Update the "Latest Release" section of www/index.html to point
> - to the new announcement.</li>
> + <li>Edit the ^/subversion/site/publish/source-code.html page to note
> + the latest release.</li>
> + <li>Add new News item to ^/subversion/site/publish/news.html
> + announcing the release. Add the same item to the News list on
> + ^/subversion/site/publish/index.html, also removing the oldest News item
> + from that page.</li>
> <li>Commit the modifications.</li>
> + <li>Create or update the versioned documentation snapshots in
> +^/site/publish/docs/api/X.Y and ^/site/publish/docs/javahl/X.Y, and
> +ensure that the "latest" symlinks which are siblings of those
> +directories always point to the directories of the latest release
> +series. Commit those changes, too.</li>
> +
> </ol>
>
> <p>If you've made it this far, go and enjoy your $favorite_beverage now.</p>
>
>
>
Re: svn commit: r963767 - /subversion/site/publish/docs/community-guide/releasing.part.html
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
On Wed, Jul 14, 2010 at 4:40 PM, Noorul Islam K M <no...@collab.net> wrote:
> "Hyrum K. Wright" <hy...@mail.utexas.edu> writes:
>
>> Bonus points if somebody writes a script to do all this website update
>> release magic for us.
>>
>
> I am trying to understand the requirement. Can you please elaborate a
> bit?
I was essentially bemoaning the fact that the release process still
has a large number of manual tools. The creation of releases is
pretty well scripted, but the other steps, such as gathering
signatures, announcing, posting the tarballs for download, and update
various links on the website, all still require a fair amount of
manual intervention. I've been meaning to get around to adding more
automation for months, but just haven't found the time (my excuse is
that I've been waiting for the move to ASF distribution infrastructure
for the 1.7 series).
I suspect that there would be a fair amount of magic involved in some
of these tasks, such as automatic website updating, but you're welcome
to dive in a give it a shot.
Best,
-Hyrum
PS - It looks as if you're trying to get involved in Subversion
development, and are looking for a task to do. The best such list of
tasks is the 'bite-sized' tasks in the issue tracker:
http://subversion.tigris.org/issues/buglist.cgi?component=subversion&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&keywords=bite-sized
Re: svn commit: r963767 - /subversion/site/publish/docs/community-guide/releasing.part.html
Posted by Noorul Islam K M <no...@collab.net>.
"Hyrum K. Wright" <hy...@mail.utexas.edu> writes:
> Bonus points if somebody writes a script to do all this website update
> release magic for us.
>
I am trying to understand the requirement. Can you please elaborate a
bit?
Thanks and Regards
Noorul
> On Tue, Jul 13, 2010 at 4:53 PM, <cm...@apache.org> wrote:
>> Author: cmpilato
>> Date: Tue Jul 13 15:53:32 2010
>> New Revision: 963767
>>
>> URL: http://svn.apache.org/viewvc?rev=963767&view=rev
>> Log:
>> * site/publish/docs/community-guide/releasing.part.html
>> (releasing-release): Update the website tweaking instructions, and
>> add a reminder to update our published API doc snapshots as part of
>> the release process, too.
>>
>> Modified:
>> subversion/site/publish/docs/community-guide/releasing.part.html
>>
>> Modified: subversion/site/publish/docs/community-guide/releasing.part.html
>> URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=963767&r1=963766&r2=963767&view=diff
>> ==============================================================================
>> --- subversion/site/publish/docs/community-guide/releasing.part.html (original)
>> +++ subversion/site/publish/docs/community-guide/releasing.part.html Tue Jul 13 15:53:32 2010
>> @@ -1062,14 +1062,19 @@ freshmeat crew before it goes public.</p
>>
>> <p><b>Update the website</b></p>
>> <ol>
>> - <li>Edit the www/project_status.html file appropriately in /trunk
>> - *NOT* in the release branch and commit. Remember edit a search term
>> - at the end of release's issue link.</li>
>> - <li>Update the best available version on the front page and at the
>> - top of www/getting.html</li>
>> - <li>Update the "Latest Release" section of www/index.html to point
>> - to the new announcement.</li>
>> + <li>Edit the ^/subversion/site/publish/source-code.html page to note
>> + the latest release.</li>
>> + <li>Add new News item to ^/subversion/site/publish/news.html
>> + announcing the release. Add the same item to the News list on
>> + ^/subversion/site/publish/index.html, also removing the oldest News item
>> + from that page.</li>
>> <li>Commit the modifications.</li>
>> + <li>Create or update the versioned documentation snapshots in
>> +^/site/publish/docs/api/X.Y and ^/site/publish/docs/javahl/X.Y, and
>> +ensure that the "latest" symlinks which are siblings of those
>> +directories always point to the directories of the latest release
>> +series. Commit those changes, too.</li>
>> +
>> </ol>
>>
>> <p>If you've made it this far, go and enjoy your $favorite_beverage now.</p>
>>
>>
>>