svn commit: r963767 - /subversion/site/publish/docs/community-guide/releasing.part.html
Author: cmpilato Date: Tue Jul 13 15:53:32 2010 New Revision: 963767 URL: http://svn.apache.org/viewvc?rev=963767view=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=963767r1=963766r2=963767view=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 pbUpdate the website/b/p ol - liEdit 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 - liUpdate the best available version on the front page and at the - top of www/getting.html/li - liUpdate the Latest Release section of www/index.html to point - to the new announcement./li + liEdit the ^/subversion/site/publish/source-code.html page to note + the latest release./li + liAdd 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 liCommit the modifications./li + liCreate 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 pIf 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
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, cmpil...@apache.org wrote: Author: cmpilato Date: Tue Jul 13 15:53:32 2010 New Revision: 963767 URL: http://svn.apache.org/viewvc?rev=963767view=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=963767r1=963766r2=963767view=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 pbUpdate the website/b/p ol - liEdit 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 - liUpdate the best available version on the front page and at the - top of www/getting.html/li - liUpdate the Latest Release section of www/index.html to point - to the new announcement./li + liEdit the ^/subversion/site/publish/source-code.html page to note + the latest release./li + liAdd 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 liCommit the modifications./li + liCreate 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 pIf you've made it this far, go and enjoy your $favorite_beverage now./p
