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 jeanTanderson
Date Fri, 26 May 2006 20:10:44 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 jeanTanderson:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

The comment on the change is:
changed more "minotaur" references to "people"

------------------------------------------------------------------------------
  
   1. Build the documentation, or grab a copy from the website.
  
-   The documentation needs to be included in the -bin distribution, so you will need a copy
of the documentation ready when running the ant release target. Information on building the
docs is located at [http://db.apache.org/derby/manuals/dita.html]. Another option, if your
release is from the main branch or the docs have not been branched yet, is to log in to minotaur.apache.org
and grab the current uploaded copy on the website, in /www/db.apache.org/derby/docs/. Tar
up the correct version of the docs into your home directory (don't leave a big tarfile in
/www/db.apache.org/derby/docs please!) and download it to your local machine with sftp. Untar
it to a local directory, that is not inside your subversion view where you are building the
release or it will be included in the -src distribution built by the release target.
+   The documentation needs to be included in the -bin distribution, so you will need a copy
of the documentation ready when running the ant release target. Information on building the
docs is located at [http://db.apache.org/derby/manuals/dita.html]. Another option, if your
release is from the main branch or the docs have not been branched yet, is to log in to people.apache.org
and grab the current uploaded copy on the website, in /www/db.apache.org/derby/docs/. Tar
up the correct version of the docs into your home directory (don't leave a big tarfile in
/www/db.apache.org/derby/docs please!) and download it to your local machine with sftp. Untar
it to a local directory, that is not inside your subversion view where you are building the
release or it will be included in the -src distribution built by the release target.
  
   1. Copy packaging.tmpl to packaging.properties in tools/release and modify as necessary.
  
@@ -212, +212 @@

  
   1. Post the distributions
  
-   Copy the files from tools/release to your public_html directory on minotaur.apache.org.
Post to derby-dev so that others can begin testing.
+   Copy the files from tools/release to your public_html directory on people.apache.org.
Post to derby-dev so that others can begin testing.
  
   1. Vote on the distributions
  
@@ -231, +231 @@

    http://www.apache.org/dev/mirrors.html and
    http://www.apache.org/dev/mirror-step-by-step.html
  
-   Copy the distribution archives and their signatures/checksums to a new directory underneath
/www/www.apache.org/dist/db/derby on minotaur.apache.org. 
+   Copy the distribution archives and their signatures/checksums to a new directory underneath
/www/www.apache.org/dist/db/derby on people.apache.org. 
  
    If the new release is the most current release, link the -current links to the new files.
Here's a quick-and-dirty shell script for doing so: 
    
@@ -268, +268 @@

    * Make sure that the .cgi script is made executable by setting svn:executable on it with
{{{svn propset svn:executable ON release-10.1.2.1.cgi}}}
    * In order for the release HTML file to be pulled into the build, it is necessary to add
a line to the <uris> section of src/documentation/conf/cli.xconf. Near line 310 of that
file, add: <uri type="append" src="releases/release-10.1.2.1.html"/> (with the correct
version for your release)
    * Due to [http://issues.apache.org/jira/browse/FOR-480]FOR-480, the release page will
be built into your $FORREST_HOME/main/site directory.
-   * Due to [http://issues.apache.org/jira/browse/FOR-555]FOR-555, the HTML comments which
constitute the form template into which the mirrors.cgi script splices in the mirror information
will be removed by Forrest. It is necessary to add these comments back in to the release page
before committing or letting the site go live on minotaur.
+   * Due to [http://issues.apache.org/jira/browse/FOR-555]FOR-555, the HTML comments which
constitute the form template into which the mirrors.cgi script splices in the mirror information
will be removed by Forrest. It is necessary to add these comments back in to the release page
before committing or letting the site go live on people.apache.org.
    * 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]).
    * Once you have committed your changes and updated the website on people, you can preview
your changes by following the instructions at http://www.apache.org/dev/project-site.html
  
@@ -276, +276 @@

  
    First, if you do not already have the latest Maven 1 distribution, download it from http://maven.apache.org/maven-1.x/start/download.html,
unpack it, and put the bin directory into your path so that you can run maven commands. As
of this writing, the latest 1.x version of Maven was 1.0.2.
  
-   Next, edit project.xml in the maven directory in the derby tree to contain the correct
version number for this release between the <currentversion> tags. Then, edit the project.properties
to contain the correct protocol, username, and password for your account on minotaur so you
can properly authenticate and copy the files to minotaur. The scpexe protocol should work
without problems, especially if you have an ssh public key already on minotaur. The project.properties
file in the maven directory should look something like this, for the maven.repo lines in the
file:
+   Next, edit project.xml in the maven directory in the derby tree to contain the correct
version number for this release between the <currentversion> tags. Then, edit the project.properties
to contain the correct protocol, username, and password for your account on people.apache.org
so you can properly authenticate and copy the files to people. The scpexe protocol should
work without problems, especially if you have an ssh public key already on people. The project.properties
file in the maven directory should look something like this, for the maven.repo lines in the
file:
  
    {{{maven.repo.list=apache
  maven.repo.apache=scpexe://svn.apache.org

Mime
View raw message