I seem to be getting closer to solving my site publish problems - I never got this far before.
However I only changed the live-sites.* so need to look at why the others got changed, sorry about that. Gav... > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Sunday, 20 August 2006 1:16 PM > To: svn@forrest.apache.org > Subject: svn commit: r432941 - in /forrest/site: ./ procedures/release/ > skin/ > > Author: gmcdonald > Date: Sat Aug 19 22:16:25 2006 > New Revision: 432941 > > URL: http://svn.apache.org/viewvc?rev=432941&view=rev > Log: > Automatic publish from forrestbot > > Modified: > forrest/site/committed-1.png > forrest/site/live-sites.html > forrest/site/live-sites.pdf > forrest/site/procedures/release/announce_code_freeze.txt > forrest/site/procedures/release/announce_end_of_code_freeze.txt > forrest/site/procedures/release/announce_release.txt > forrest/site/procedures/release/propose_release_plan.txt > forrest/site/procedures/release/rc_did_not_build_what_now.txt > forrest/site/procedures/release/test_and_vote_on_rel_cand.txt > forrest/site/skin/basic.css > forrest/site/skin/print.css > forrest/site/skin/profile.css > forrest/site/skin/screen.css > > Modified: forrest/site/committed-1.png > URL: http://svn.apache.org/viewvc/forrest/site/committed- > 1.png?rev=432941&r1=432940&r2=432941&view=diff > ========================================================================== > ==== > Binary files - no diff available. > > Modified: forrest/site/live-sites.html > URL: http://svn.apache.org/viewvc/forrest/site/live- > sites.html?rev=432941&r1=432940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/live-sites.html (original) > +++ forrest/site/live-sites.html Sat Aug 19 22:16:25 2006 > @@ -544,9 +544,7 @@ > <ul> > > <li> > -<a href="http://floatingsun.net/";>Diwaker Gupta :: > - Web/Blog/Gallery</a> > -</li> > +<a href="http://floatingsun.net/";>Floating Sun</a>Diwaker Gupta :: > Web/Blog/Gallery</li> > > <li> > <a href="http://www.ourlittlestars.org/";>Our Little Stars</a> - A non- > profit toy library site. > > Modified: forrest/site/live-sites.pdf > URL: http://svn.apache.org/viewvc/forrest/site/live- > sites.pdf?rev=432941&r1=432940&r2=432941&view=diff > ========================================================================== > ==== > Binary files - no diff available. > > Modified: forrest/site/procedures/release/announce_code_freeze.txt > URL: > http://svn.apache.org/viewvc/forrest/site/procedures/release/announce_code > _freeze.txt?rev=432941&r1=432940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/procedures/release/announce_code_freeze.txt (original) > +++ forrest/site/procedures/release/announce_code_freeze.txt Sat Aug 19 > 22:16:25 2006 > @@ -2,39 +2,39 @@ > > Table Of Contents > ================= > -Subject: [Important] code-freeze commenced > - > -The code-freeze is now happening to allow us to pack the > -release candidates and make them available for testing. > - > -Code-freeze means *no* non-essential commits to the trunk > -or to the new release branch. Other branches are free to > -continue. > - > -There should be no code enhancements or new functionality, > -because that could introduce new bugs. > - > -The main aim is to find and fix important bugs. Any minor > -issues are delayed until after release (add to Jira). > - > -Documentation corrections can happen because they will not > -break anything. As long as we do test the documentation > -building just prior to making the final release candidate. > - > -However, if there are important code changes that are > -required you can make a proposal to allow that commit. > -The Release Manager will make a quick decision. > - > -Next important milestones are: > - > -* Create release candidate #2 if there have been changes > - on [date] > - [www.timeanddate.com-URL] > - > -* Actual release date is [date] > - [www.timeanddate.com-URL] > - > -Now we will go and build the releases which might take > -some time. The next message will tell you where to get > +Subject: [Important] code-freeze commenced > + > +The code-freeze is now happening to allow us to pack the > +release candidates and make them available for testing. > + > +Code-freeze means *no* non-essential commits to the trunk > +or to the new release branch. Other branches are free to > +continue. > + > +There should be no code enhancements or new functionality, > +because that could introduce new bugs. > + > +The main aim is to find and fix important bugs. Any minor > +issues are delayed until after release (add to Jira). > + > +Documentation corrections can happen because they will not > +break anything. As long as we do test the documentation > +building just prior to making the final release candidate. > + > +However, if there are important code changes that are > +required you can make a proposal to allow that commit. > +The Release Manager will make a quick decision. > + > +Next important milestones are: > + > +* Create release candidate #2 if there have been changes > + on [date] > + [www.timeanddate.com-URL] > + > +* Actual release date is [date] > + [www.timeanddate.com-URL] > + > +Now we will go and build the releases which might take > +some time. The next message will tell you where to get > the release candidates and describe how to test. > > > Modified: forrest/site/procedures/release/announce_end_of_code_freeze.txt > URL: > http://svn.apache.org/viewvc/forrest/site/procedures/release/announce_end_ > of_code_freeze.txt?rev=432941&r1=432940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/procedures/release/announce_end_of_code_freeze.txt > (original) > +++ forrest/site/procedures/release/announce_end_of_code_freeze.txt Sat > Aug 19 22:16:25 2006 > @@ -2,8 +2,8 @@ > > Table Of Contents > ================= > -Subject: [Important] End of code-freeze > - > -The code-freeze has ended. > +Subject: [Important] End of code-freeze > + > +The code-freeze has ended. > > > > Modified: forrest/site/procedures/release/announce_release.txt > URL: > http://svn.apache.org/viewvc/forrest/site/procedures/release/announce_rele > ase.txt?rev=432941&r1=432940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/procedures/release/announce_release.txt (original) > +++ forrest/site/procedures/release/announce_release.txt Sat Aug 19 > 22:16:25 2006 > @@ -2,12 +2,12 @@ > > Table Of Contents > ================= > -To: > dev@forrest.apache.org,user@forrest.apache.org,announce@apache.org,announc > [EMAIL PROTECTED] > -Subject: [Announce] Apache Forrest X.Y.Z > - > - !! Always refer them to the mirror facility > - !! Never mention the URL www.apache.org/ dist/ in email or web > pages. > - Use the template at etc/announcement.txt > - Use your spelling checker! > +To: > dev@forrest.apache.org,user@forrest.apache.org,announce@apache.org,announc > [EMAIL PROTECTED] > +Subject: [Announce] Apache Forrest X.Y.Z > + > + !! Always refer them to the mirror facility > + !! Never mention the URL www.apache.org/ dist/ in email or web > pages. > + Use the template at etc/announcement.txt > + Use your spelling checker! > Sign the email (e.g. GPG) if possible. > > > Modified: forrest/site/procedures/release/propose_release_plan.txt > URL: > http://svn.apache.org/viewvc/forrest/site/procedures/release/propose_relea > se_plan.txt?rev=432941&r1=432940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/procedures/release/propose_release_plan.txt (original) > +++ forrest/site/procedures/release/propose_release_plan.txt Sat Aug 19 > 22:16:25 2006 > @@ -2,55 +2,55 @@ > > Table Of Contents > ================= > -FIXME: http://www.mail-archive.com/dev@forrest.apache.org/msg02310.html > -incorporate that into this > - > -Subject: [VOTE] Release Plan for Forrest x.xx > - > -We are about to work on releasing a new version of Forrest. > -Below I have proposed the important milestones. > - > -Please check with your time schedules and comment. > -We want to have as many people available as possible > -to test the release candidate. So we can adjust the > -time schedule a bit. > - > -Please vote on this release plan. > - > -Proposed Java version to test this release is [Version]. > - > -Proposed milestones are: > - > -- Start of code-freeze on [Date] > - [www.timeanddate.com-URL] > - > -- Start of test-period [Date] > - [www.timeanddate.com-URL] > - > -- Vote on release candidate #1 [Date] > - [www.timeanddate.com-URL] > - > -- Start of test-period [Date] > - [www.timeanddate.com-URL] > - > -- Vote on release candidate [Date] > - [www.timeanddate.com-URL] > - > -- If there are bugs in RC1 > - > - = Creation of release candidate #2 > - (only when there are bugs) [Date] > - [www.timeanddate.com-URL] > - > - = Start of test-period #2 [Date] > - [www.timeanddate.com-URL] > +FIXME: http://www.mail-archive.com/dev@forrest.apache.org/msg02310.html > +incorporate that into this > + > +Subject: [VOTE] Release Plan for Forrest x.xx > + > +We are about to work on releasing a new version of Forrest. > +Below I have proposed the important milestones. > + > +Please check with your time schedules and comment. > +We want to have as many people available as possible > +to test the release candidate. So we can adjust the > +time schedule a bit. > + > +Please vote on this release plan. > > - = Vote on release candidate #2 [Date] > - [www.timeanddate.com-URL] > - > -- Scheduled release Date [Date] > - [www.timeanddate.com-URL] > - > -For background info on this step and the release process in general see > +Proposed Java version to test this release is [Version]. > + > +Proposed milestones are: > + > +- Start of code-freeze on [Date] > + [www.timeanddate.com-URL] > + > +- Start of test-period [Date] > + [www.timeanddate.com-URL] > + > +- Vote on release candidate #1 [Date] > + [www.timeanddate.com-URL] > + > +- Start of test-period [Date] > + [www.timeanddate.com-URL] > + > +- Vote on release candidate [Date] > + [www.timeanddate.com-URL] > + > +- If there are bugs in RC1 > + > + = Creation of release candidate #2 > + (only when there are bugs) [Date] > + [www.timeanddate.com-URL] > + > + = Start of test-period #2 [Date] > + [www.timeanddate.com-URL] > + > + = Vote on release candidate #2 [Date] > + [www.timeanddate.com-URL] > + > +- Scheduled release Date [Date] > + [www.timeanddate.com-URL] > + > +For background info on this step and the release process in general see > > http://forrest.apache.org/procedures/release/How_to_release.html#PrepRelPl > an > > > Modified: forrest/site/procedures/release/rc_did_not_build_what_now.txt > URL: > http://svn.apache.org/viewvc/forrest/site/procedures/release/rc_did_not_bu > ild_what_now.txt?rev=432941&r1=432940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/procedures/release/rc_did_not_build_what_now.txt > (original) > +++ forrest/site/procedures/release/rc_did_not_build_what_now.txt Sat Aug > 19 22:16:25 2006 > @@ -2,13 +2,13 @@ > > Table Of Contents > ================= > -Subject: [Important] Release Candidate did NOT build, what now? > - > -The release candidate/documentation for the new release failed the tests. > -A quick attempt at to solve the problems has failed. > - > -What shall we do now? > - > -If anybody can suggest a solution please do, otherwise we will have to > abort > +Subject: [Important] Release Candidate did NOT build, what now? > + > +The release candidate/documentation for the new release failed the tests. > +A quick attempt at to solve the problems has failed. > + > +What shall we do now? > + > +If anybody can suggest a solution please do, otherwise we will have to > abort > this release attempt for now and write up a new release plan. > > > Modified: forrest/site/procedures/release/test_and_vote_on_rel_cand.txt > URL: > http://svn.apache.org/viewvc/forrest/site/procedures/release/test_and_vote > _on_rel_cand.txt?rev=432941&r1=432940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/procedures/release/test_and_vote_on_rel_cand.txt > (original) > +++ forrest/site/procedures/release/test_and_vote_on_rel_cand.txt Sat Aug > 19 22:16:25 2006 > @@ -2,64 +2,64 @@ > > Table Of Contents > ================= > -Subject: [Important] please test release candidate then vote > - > -We need people to test the release candidate on your projects, > -especially on different operating systems. Just send a short > -reply to this thread that it works for you. See method below. > - > -Download the release candidate and supporting files: > -http://people.apache.org/~[your apache user name]/release-forrest-07/ > - > -For Windows get *.zip md5sum ################################ > -For UNIX get *.tar.gz md5sum ################################ > -Get the *.asc and *.md5 that match your chosen download. > - > -It was packed from SVN revision #### > -Java [JavaVersion] or later is required. > - > -If you want to verify the download, then follow: > -http://forrest.apache.org/mirrors.cgi#verify > - > -Otherwise just get on with testing. > - > -Testing and vote period concludes [Date] > -Anyone can test and vote, not just PMC members. > -However only the PMC votes are binding. > -When voting, quote the md5sum to ensure that we are all > -using the correct release candidate. > - > -So we have approximately 6 days. > - > -Here are some hints: > - > - * Ensure that the compressed archive will unpack properly. > - * Verfiy the release, especially if you are a committer. > - * Follow the README.txt and index.html > - * Set $FORREST_HOME and $PATH appropriately. > - * Many known issues are already recorded at our Jira. > - * Don't worry too much about minor bugs. We are looking > - for blockers, such as it will not run. > - * Please add minor issues to Jira. > - > -* Make a fresh site ... > - cd my-new-dir > - forrest seed > - forrest run ... use the local jetty server. > - forrest ... build the whole site from the command-line. > - forrest war ... use your own full Jetty or Tomcat. > - > -* Try it on the Forrest core docs ... > - cd site-author > - forrest run > - forrest > - > -* Forrest was already pre-built. Try building it again. > - cd main > - build clean > - build > - build test > - > -* Try it on your own project, especially if you have > +Subject: [Important] please test release candidate then vote > + > +We need people to test the release candidate on your projects, > +especially on different operating systems. Just send a short > +reply to this thread that it works for you. See method below. > + > +Download the release candidate and supporting files: > +http://people.apache.org/~[your apache user name]/release-forrest-07/ > + > +For Windows get *.zip md5sum ################################ > +For UNIX get *.tar.gz md5sum ################################ > +Get the *.asc and *.md5 that match your chosen download. > + > +It was packed from SVN revision #### > +Java [JavaVersion] or later is required. > + > +If you want to verify the download, then follow: > +http://forrest.apache.org/mirrors.cgi#verify > + > +Otherwise just get on with testing. > + > +Testing and vote period concludes [Date] > +Anyone can test and vote, not just PMC members. > +However only the PMC votes are binding. > +When voting, quote the md5sum to ensure that we are all > +using the correct release candidate. > + > +So we have approximately 6 days. > + > +Here are some hints: > + > + * Ensure that the compressed archive will unpack properly. > + * Verfiy the release, especially if you are a committer. > + * Follow the README.txt and index.html > + * Set $FORREST_HOME and $PATH appropriately. > + * Many known issues are already recorded at our Jira. > + * Don't worry too much about minor bugs. We are looking > + for blockers, such as it will not run. > + * Please add minor issues to Jira. > + > +* Make a fresh site ... > + cd my-new-dir > + forrest seed > + forrest run ... use the local jetty server. > + forrest ... build the whole site from the command-line. > + forrest war ... use your own full Jetty or Tomcat. > + > +* Try it on the Forrest core docs ... > + cd site-author > + forrest run > + forrest > + > +* Forrest was already pre-built. Try building it again. > + cd main > + build clean > + build > + build test > + > +* Try it on your own project, especially if you have > a project sitemap and use some extra plugins. > > > Modified: forrest/site/skin/basic.css > URL: > http://svn.apache.org/viewvc/forrest/site/skin/basic.css?rev=432941&r1=432 > 940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/skin/basic.css (original) > +++ forrest/site/skin/basic.css Sat Aug 19 22:16:25 2006 > @@ -162,4 +162,4 @@ > .codefrag { > font-family: "Courier New", Courier, monospace; > font-size: 110%; > -} > \ No newline at end of file > +} > > Modified: forrest/site/skin/print.css > URL: > http://svn.apache.org/viewvc/forrest/site/skin/print.css?rev=432941&r1=432 > 940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/skin/print.css (original) > +++ forrest/site/skin/print.css Sat Aug 19 22:16:25 2006 > @@ -51,4 +51,4 @@ > > acronym { > border: 0; > -} > \ No newline at end of file > +} > > Modified: forrest/site/skin/profile.css > URL: > http://svn.apache.org/viewvc/forrest/site/skin/profile.css?rev=432941&r1=4 > 32940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/skin/profile.css (original) > +++ forrest/site/skin/profile.css Sat Aug 19 22:16:25 2006 > @@ -150,4 +150,4 @@ > /* extra-css */ > #footer a { color: #0F3660; } > #footer a:visited { color: #009999; } > - > \ No newline at end of file > + > > Modified: forrest/site/skin/screen.css > URL: > http://svn.apache.org/viewvc/forrest/site/skin/screen.css?rev=432941&r1=43 > 2940&r2=432941&view=diff > ========================================================================== > ==== > --- forrest/site/skin/screen.css (original) > +++ forrest/site/skin/screen.css Sat Aug 19 22:16:25 2006 > @@ -583,4 +583,4 @@ > list-style-image: url('../images/instruction_arrow.png'); > list-style-position: outside; > margin-left: 2em; > -} > \ No newline at end of file > +} > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.405 / Virus Database: 268.11.3/423 - Release Date: 8/18/2006
