forrest-site-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r550345 - in /forrest/site: ./ docs_0_90/ dtdx/ procedures/ procedures/release/ skin/
Date Mon, 25 Jun 2007 04:48:59 GMT
Author: crossley
Date: Sun Jun 24 21:48:57 2007
New Revision: 550345

URL: http://svn.apache.org/viewvc?view=rev&rev=550345
Log:
Automatic publish from forrestbot

Modified:
    forrest/site/committed-1.png
    forrest/site/docs_0_90/linking.pdf
    forrest/site/docs_0_90/primer.pdf
    forrest/site/docs_0_90/your-project.html
    forrest/site/docs_0_90/your-project.pdf
    forrest/site/dtdx/document-v12.pdf
    forrest/site/dtdx/document-v13.pdf
    forrest/site/dtdx/document-v20.pdf
    forrest/site/procedures/How_to_publish_docs.html
    forrest/site/procedures/How_to_publish_docs.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?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_90/linking.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_90/linking.pdf?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_90/primer.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_90/primer.pdf?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_90/your-project.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_90/your-project.html?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/docs_0_90/your-project.html (original)
+++ forrest/site/docs_0_90/your-project.html Sun Jun 24 21:48:57 2007
@@ -1692,7 +1692,7 @@
       </p>
 </div>
   
-<span class="version">SVN: $Revision: 536444 $ $Date: 2007-05-09 14:34:45 +0800 (Wed,
09 May 2007) $</span>
+<span class="version">SVN: $Revision: 536444 $ $Date: 2007-05-09 16:34:45 +1000 (Wed,
09 May 2007) $</span>
 </div>
 <!--+
     |end content

Modified: forrest/site/docs_0_90/your-project.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_90/your-project.pdf?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
Binary files - no diff available.

Modified: forrest/site/dtdx/document-v12.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v12.pdf?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
Binary files - no diff available.

Modified: forrest/site/dtdx/document-v13.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v13.pdf?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
Binary files - no diff available.

Modified: forrest/site/dtdx/document-v20.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v20.pdf?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
Binary files - no diff available.

Modified: forrest/site/procedures/How_to_publish_docs.html
URL: http://svn.apache.org/viewvc/forrest/site/procedures/How_to_publish_docs.html?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/procedures/How_to_publish_docs.html (original)
+++ forrest/site/procedures/How_to_publish_docs.html Sun Jun 24 21:48:57 2007
@@ -262,7 +262,7 @@
 <p>
         All documentation about Apache Forrest is managed as a Forrest-built
         project located in the site-author directory of forrest/trunk SVN. The
-        Apache Forrest website is updated by generating static pages from the
+        Apapce Forrest website is updated by generating static pages from the
         site-author-project and committing them to the forrest/site SVN, which
         is then 'svn checkout' on the forrest.apache.org webserver to create the
         website.
@@ -399,6 +399,12 @@
 forrest -f publish.xml build
 svn update work/svn-deploy/forrest-docs
 diff -rq build/forrest-docs work/svn-deploy/forrest-docs | grep -v "\.svn" | grep differ</pre>
+<p>
+        If you change something that affects all pages (e.g. layout changes; navigation
+        menu additions or MOTD changes that affect old "versioned docs")
+        then see the note in conf/cli.xconf about temporarily not excluding
+        old "docs_*" patterns.
+      </p>
 </div>
   
 </div>

Modified: forrest/site/procedures/How_to_publish_docs.pdf
URL: http://svn.apache.org/viewvc/forrest/site/procedures/How_to_publish_docs.pdf?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
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?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/procedures/release/announce_code_freeze.txt (original)
+++ forrest/site/procedures/release/announce_code_freeze.txt Sun Jun 24 21:48:57 2007
@@ -2,46 +2,46 @@
 
 Table Of Contents
 =================
-Subject: [Important] code-freeze commenced 
- 
-The code-freeze is now happening to allow us to prepare the 
-release candidate packages 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. Whiteboard plugins can also 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. 
-Although remember that such work should have happened 
-prior to the code-freeze. We don't want to build subsequent 
-release candidates unless necessary. 
- 
-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 the Release Manager will do some final changes, such 
-as license header checks, xml code cleanup, and changing 
-version number information. Then the RM will build the 
-packages. These steps may take some time. 
- 
-The next message will tell you where to downlaod the 
+Subject: [Important] code-freeze commenced
+
+The code-freeze is now happening to allow us to prepare the
+release candidate packages 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. Whiteboard plugins can also 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.
+Although remember that such work should have happened
+prior to the code-freeze. We don't want to build subsequent
+release candidates unless necessary.
+
+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 the Release Manager will do some final changes, such
+as license header checks, xml code cleanup, and changing
+version number information. Then the RM will build the
+packages. These steps may take some time.
+
+The next message will tell you where to downlaod the
 release candidate packages 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?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/procedures/release/announce_end_of_code_freeze.txt (original)
+++ forrest/site/procedures/release/announce_end_of_code_freeze.txt Sun Jun 24 21:48:57 2007
@@ -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_release.txt?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/procedures/release/announce_release.txt (original)
+++ forrest/site/procedures/release/announce_release.txt Sun Jun 24 21:48:57 2007
@@ -2,12 +2,12 @@
 
 Table Of Contents
 =================
-To: dev@forrest.apache.org,user@forrest.apache.org,announce@apache.org,announcements@xml.apache.org

-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,announcements@xml.apache.org
+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_release_plan.txt?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/procedures/release/propose_release_plan.txt (original)
+++ forrest/site/procedures/release/propose_release_plan.txt Sun Jun 24 21:48:57 2007
@@ -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. 
+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]
     
-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  
+    = 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#PrepRelPlan
 

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_build_what_now.txt?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/procedures/release/rc_did_not_build_what_now.txt (original)
+++ forrest/site/procedures/release/rc_did_not_build_what_now.txt Sun Jun 24 21:48:57 2007
@@ -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?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/procedures/release/test_and_vote_on_rel_cand.txt (original)
+++ forrest/site/procedures/release/test_and_vote_on_rel_cand.txt Sun Jun 24 21:48:57 2007
@@ -2,92 +2,92 @@
 
 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 and Java version. 
-Just send a short reply to this thread that it works for you. 
-See testing hints below. 
- 
-Download the release candidate and supporting files: 
-http://people.apache.org/~[### your apache ID ###]/temp/forrest-###08###-rc1/ 
- 
-For Windows get *.zip md5sum ################################ 
-For UNIX get *.tar.gz md5sum ################################ 
-Get the *.asc and *.md5 that match your chosen download. 
- 
-Java [### JavaVersion ###] or later is required. 
- 
-Testing and vote period concludes [#### Date #####] [2]. 
-Anyone can test and vote, not just PMC members. 
-However only the PMC votes are binding [3]. 
- 
-When voting, quote the md5sum to ensure that we are all 
-using the correct release candidate package. The votes 
-need to happen against the final release package. 
- 
-PMC members need to satisfy themselves that the actual 
-final release package meets the ASF principles. 
- 
-Please wait with voting until towards the end of the 
-week, as we may need to build a second release candidate 
-if there are any changes to the code or documentation [1]. 
- 
-During this week we do need to hear about successes 
-or failures. Please report your operating system 
-and Java versions and Jetty/Tomcat versions. 
- 
-So we have approximately 6 days. 
- 
-Here are some hints: 
- 
-  * Verfiy the release, especially if you are a committer. 
-    Follow: http://forrest.apache.org/mirrors.cgi#verify 
-  * Ensure that the compressed archive will unpack properly. 
-  * Follow the README.txt and index.html 
-  * Set $FORREST_HOME and $PATH appropriately. 
-  * Try it with different Java versions. 
-  * Try it with different versions of Apache Tomcat or Jetty. 
-  * 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 other discovered 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. 
- 
-* If you are a user of forrestbot then try that. 
- 
-* Try building and installing the forrestbar. 
- 
------------------------------- 
-[1] create final release candidate 
-Saturday 2007-04-14 at 22:00 UTC 
-[### time-and-date URL ###] 
- 
-[2] end of vote on final release candidate and commence the upload phase 
-Monday 2007-04-16 at 22:00 UTC 
-[### time-and-date URL ###] 
- 
-[3] "A lazy majority vote requires 
-3 binding +1 votes and more binding +1 votes than -1 votes". 
+Subject: [Important] please test release candidate then vote
+
+We need people to test the release candidate on your projects,
+especially on different operating systems and Java version.
+Just send a short reply to this thread that it works for you.
+See testing hints below.
+
+Download the release candidate and supporting files:
+http://people.apache.org/~[### your apache ID ###]/temp/forrest-###08###-rc1/
+
+For Windows get *.zip md5sum ################################
+For UNIX get *.tar.gz md5sum ################################
+Get the *.asc and *.md5 that match your chosen download.
+
+Java [### JavaVersion ###] or later is required.
+
+Testing and vote period concludes [#### Date #####] [2].
+Anyone can test and vote, not just PMC members.
+However only the PMC votes are binding [3].
+
+When voting, quote the md5sum to ensure that we are all
+using the correct release candidate package. The votes
+need to happen against the final release package.
+
+PMC members need to satisfy themselves that the actual
+final release package meets the ASF principles.
+
+Please wait with voting until towards the end of the
+week, as we may need to build a second release candidate
+if there are any changes to the code or documentation [1].
+
+During this week we do need to hear about successes
+or failures. Please report your operating system
+and Java versions and Jetty/Tomcat versions.
+
+So we have approximately 6 days.
+
+Here are some hints:
+
+  * Verfiy the release, especially if you are a committer.
+    Follow: http://forrest.apache.org/mirrors.cgi#verify
+  * Ensure that the compressed archive will unpack properly.
+  * Follow the README.txt and index.html
+  * Set $FORREST_HOME and $PATH appropriately.
+  * Try it with different Java versions.
+  * Try it with different versions of Apache Tomcat or Jetty.
+  * 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 other discovered 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.
+
+* If you are a user of forrestbot then try that.
+
+* Try building and installing the forrestbar.
+
+------------------------------
+[1] create final release candidate
+Saturday 2007-04-14 at 22:00 UTC
+[### time-and-date URL ###]
+
+[2] end of vote on final release candidate and commence the upload phase
+Monday 2007-04-16 at 22:00 UTC
+[### time-and-date URL ###]
+
+[3] "A lazy majority vote requires
+3 binding +1 votes and more binding +1 votes than -1 votes".
 http://forrest.apache.org/guidelines.html#actions
 

Modified: forrest/site/skin/basic.css
URL: http://svn.apache.org/viewvc/forrest/site/skin/basic.css?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/skin/basic.css (original)
+++ forrest/site/skin/basic.css Sun Jun 24 21:48:57 2007
@@ -163,4 +163,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?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/skin/print.css (original)
+++ forrest/site/skin/print.css Sun Jun 24 21:48:57 2007
@@ -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?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/skin/profile.css (original)
+++ forrest/site/skin/profile.css Sun Jun 24 21:48:57 2007
@@ -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?view=diff&rev=550345&r1=550344&r2=550345
==============================================================================
--- forrest/site/skin/screen.css (original)
+++ forrest/site/skin/screen.css Sun Jun 24 21:48:57 2007
@@ -455,12 +455,17 @@
 }
 
 #motd-area {
+    position: relative; /* IE bugfix cont'd */
+    float: right;
     width: 35%;
     background-color: #f0f0ff;
     border-top: solid 1px #4C6C8F;
     border-bottom: solid 1px #4C6C8F;
-    margin: 15px;
-    padding: 5px;
+    margin-bottom: 15px;
+    margin-left: 15px;
+    margin-right: 10%;
+    padding-bottom: 5px;
+    padding-top: 5px;
 }
 
 #minitoc-area {
@@ -579,4 +584,4 @@
   list-style-image: url('../images/instruction_arrow.png');
   list-style-position: outside;
   margin-left: 2em;
-} 
+} 
\ No newline at end of file



Mime
View raw message