Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Thu, 01 May 2008 15:17:40 -0000
Message-ID: <20080501151740.5790.38975@eos.apache.org>
Subject: [Db-derby Wiki] Update of "DerbySnapshotOrRelease" by DyreTjeldvoll

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

------------------------------------------------------------------------------
  
    Call for a vote on derby-dev to have the distributions posted on your `public_html` accepted for the release. 
  
-   {i} It is not always easy to dechipher all the voting rules which govern the acceptance/rejection of a release candidate. First there is the [http://www.apache.org/foundation/voting.html Apache rules for releases], the [http://db.apache.org/decisions.html DB decision guidelines], and finally the [http://db.apache.org/management.html DB PMC Bylaws]. 
+   {i} It is not always easy to decipher all the voting rules which govern the acceptance/rejection of a release candidate. First there are the [http://www.apache.org/foundation/voting.html Apache rules for releases], the [http://db.apache.org/decisions.html DB decision guidelines], and finally the [http://db.apache.org/management.html DB PMC Bylaws]. 
  
    The existing practice is: A vote needs to be running for at least 7 days, so, give at least that much time before closing the vote to give adequate time for others to inspect and test the distributions. If no-one has responded after a week, prod gently until you get a response. A majority of votes, and at least one binding +1 vote are required for acceptance.
  
@@ -449, +449 @@

  
    using db-derby-10.1.1.0 as the release to link to -current as an example.
  
+  1. Copy the latest version of the documentation to the doc directory on the website. 
+   The documentation is included in the release you uploaded, but unfortunately its directory structure quite right for the website. To get around this you need to unzip the db-derby-x.y.z.w-bin.zip archive, rename some directories and copy the pdf files into the html hierarchy. Here is a shell script describing the process:
+ 
+   {{{
+ #! /bin/bash
+ mkdir ~/x.y
+ cd ~/x.y
+ unzip $1
+ mv db*bin/docs .
+ mv db*bin/javadoc ./publishedapi
+ rm -r db*bin
+ 
+ for i in adminguide devguide getstart ref tools tuning
+ do
+   mv docs/pdf/$i/*.pdf docs/html/$i
+   rmdir docs/pdf/$i
+ done
+ 
+ mv docs/html/* .
+ rmdir docs/html
+ rmdir docs/pdf/pt_BR
+ rmdir docs/pdf
+ rmdir docs
+ }}}
+ 
+ Pass in the location of the `db-derby-x.y.z.w-bin.zip`. Move the x.y directory that
+ gets created in your home directory over to `/www/db.apache.org/derby/docs`.
+ 
+   (!) A raw recursive copy using scp is going to take a long time, so a better approach would be to create and archive and copy that:
+   {{{ zip -r x.y.zip x.y
+ scp x.y.zip you@people.apache.org:/www/db.apache.org/derby/docs/
+ ssh you@people.apache.org
+ cd /www/db.apache.org/derby/docs/
+ unzip x.y.zip
+ rm x.y.zip }}}
   
   1. Create a page for the release, build/update site