db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbySnapshotOrRelease" by DyreTjeldvoll
Date Thu, 01 May 2008 17:46:08 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DyreTjeldvoll:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

------------------------------------------------------------------------------
  
    a. Add a mirroring CGI script for the release. The CGI file should have the same name
as the HTML file, but obviously a `.cgi` extension.
     (!) The easiest thing is probably just to copy the CGI script for an existing release.

-    * Forrest will not copy the release CGI script over unless you make a link to it from
another page. Add the link to derby_downloads.html, as described below, before building.
+    * Forrest will not copy the release CGI script over unless you make a link to it from
another page. Add the link to `derby_downloads.html`, as described below, before building.
-    * Make sure that the CGI script is made executable by setting svn:executable on it 
+    * Make sure that the CGI script is made executable by setting `svn:executable` on it

  
     {{{cd src/documentation/content/xdocs/releases 
  cp release-x'.y'.z'.w'.cgi release-x.y.z.w.cgi
  svn add release-x.y.z.w.cgi      
- svn propset svn:executable ON release-x.y.z.w.cgi }}}. 
+ svn propset svn:executable ON release-x.y.z.w.cgi }}}
  
     <!> Be sure to set `svn:executable` also for the generated copy which forrest builds
into `build/site/releases`.
  
@@ -529, +529 @@

  svn delete release-x'.y'.z'.w'.cgi
  vi release-x'.y'.z'.w'.html }}}
  
-   a. Update the `derby_downloads.xml` page in the `src/documentation/content/xdocs` directory
so that the links to the new files are included.
- 
+   a. Update `src/documentation/content/xdocs/derby_downloads.xml`:
+     * Add a link to the CGI script for the new release at the top of the releases section.
+     * Move the previous release down to the other old releases.
+     * Change the link from the CGI script to the HTML file for all releases for which you
disabled mirroring (in the previous step).
+  
    a. Run 'forrest site' at the top of the site tree.
     {i} [http://db.apache.org/derby/papers/derby_web.html Forrest instructions]
  
@@ -538, +541 @@

  
     {X} The build process frequently will create "false modifications" in `build/tmp` or
`build/site/skin`. These must be reverted before checking in the changes. Subversion may report
some files as changed which should be static. Revert anything in build/site/skin or build/site/papers
before committing your website changes ([http://db.apache.org/derby/papers/derby_web.html#odd_diffs
see the explanation]).
  
-    {{{cd webtrunk
- rm -rf $FORREST_HOME/main/site/*  # Remove any files from a previous build
+    {{{rm -rf $FORREST_HOME/main/site/*  # Remove any files from a previous build
  forrest site
  cp -r $FORREST_HOME/main/site build/site
  svn revert -R build/tmp build/site/skin
@@ -553, +555 @@

  cd /www/db.apache.org/derby
  svn up}}}
  
-    <!> Note that `people.apache.org` is rsync'd to the actual website every hour or
so. Verify that the new release appears on the [http://db.apache.org/derby/derby_downloads.html
Derby download page]. Also check you still can download any release for which you disabled
mirroring. Finally check that you can access the new documentation at the [http://db.apache.org/derby/manuals/index.html
documentation page].
+    <!> Note that `people.apache.org` is rsync'd to the actual website every hour or
so. Verify that the new release appears on the [http://db.apache.org/derby/derby_downloads.html
download page]. Also check you still can download any release for which you disabled mirroring.
Finally check that you can access the new documentation at the [http://db.apache.org/derby/manuals/index.html
documentation page].
  
     <!> Also, when you run 'svn up' on people.apache.org, make sure that the new .cgi
file is executable and otherwise has the correct permissions!
  
    a. Once you have committed your changes and updated the website on people, you can review
your changes by following the instructions at http://www.apache.org/dev/project-site.html
  
    a. If you removed mirroring for an existing release (by removing the CGI script and changing
the links), you should now delete those releases from the mirror directory as it is important
to keep the mirror directory tidy. 
-    <!> Don't delete them until you have verified that the updated web page with new
links to the archive directory actually works.
+    <!> Don't delete them until you have verified that the updated web page with new
links to the archive directory actually works!
  
     {i} It is no longer necessary to manually copy releases to the archive. Anything placed
in the mirror directory (`/www/www.apache.org/dist/db/derby`) will automatically be copied
to the archive directory (`/www/archive.apache.org/dist/db/derby`).
   

Mime
View raw message