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, <[email protected]> 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> > > >
