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 KatheyMarsden
Date Wed, 12 Dec 2007 18:02:26 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 KatheyMarsden:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

The comment on the change is:
make some minor changes to the release pages. 

------------------------------------------------------------------------------
  
    And comparing the output of openssl to the output from ant in db-derby-10.1.1.0-src.zip.md5
  
+ Keep the jars/insane/*.jar files available. You will need them for maven deployment after
the vote is complete.
+ 
   1. Bump the fourth digit of the source in preparation for a possible next build; update
the masters
    You should update tools/ant/properties/release.properties by hand and then run:
    {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties
tools/release/maintversion.properties
@@ -397, +399 @@

   It is a good idea to use the previous release pages as templates, filling in the changed
details as necessary. You should add a .cgi and a .html file for the release. The main thing
to remember is that the .cgi file should have the same name as the .html file. 
  
   a. Update the derby_downloads.xml page in the src/documentation/content/xdocs directory
so that the links to the new files are included.
- 
-  b. Run 'forrest site' at the top of the site tree.
- 
-  c. Check the changes. If they look good, 'svn commit' them. NOTE: you should revert any
changed files in build/tmp or build/site/skin. But you should check in other updated files.
- 
-  d. Update the website on people.apache.org by logging into the machine and doing:
- 
-  {{{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 changes appear on the Derby website at http://db.apache.org/derby/derby_downloads.html
- 
-   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!
- 
-   Note the following things when creating the release page:
+  Note the following things when creating the release page:
    * Be sure to specify that the src.tar.gz requires gnu tar to unravel (because of our usage
of ant tar to create this, using longfile=gnu for handling long filenames).
    * 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 before building.
    * Remove all square brackets [] from the release notes page. When the cgi machinery sees
square brackets, it truncates the release page.
@@ -419, +407 @@

  svn:executable ON release-10.1.2.1.cgi}}}. Be sure to do this for both the precursor version
you created in src/documentation/content/xdocs/releases and for the generated copy which forrest
builds into build/site/releases.
    * 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-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.
-   * 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.
    * Svn delete the cgi script for the previous release. Also, edit its release page to remove
the cgi boilerplate and convert the distribution links from mirror references to ordinary
links. This means removing the [preferred] tags. To see what this should look like, look at
the release page for an even older release.
    * 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]).
+  b. Run 'forrest site' at the top of the site tree.
+ 
+  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. You will need to copy it to the build directory.
+ 
+  c. Check the changes. If they look good, 'svn commit' them. NOTE: you should revert any
changed files in build/tmp or build/site/skin. But you should check in other updated files.
+ 
+  d. Update the website on people.apache.org by logging into the machine and doing:
+ 
+  {{{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 changes appear on the Derby website at http://db.apache.org/derby/derby_downloads.html
+ 
+   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!
+ 
-   * 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
+   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
  
  
   1. Deploy to Maven repository.
  
-   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.
+   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.1.
  
    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:
  
@@ -438, +440 @@

  maven.repo.apache.password={your_password}
  maven.repo.apache.group=db}}}
  
-   Also, make sure you have the maven artifact plugin, version 1.5.2, so that maven generates
SHA1 checksums for the files you upload, by running the following command:
- 
-   {{{maven plugin:download -DgroupId=maven \
-   -DartifactId=maven-artifact-plugin \
-   -Dversion=1.5.2}}}
- 
-   NOTE: this should only be necessary for Maven 1.0.2. The latest artifact plugin will be
included in future stable releases of Maven 1.x.
- 
    Then, cd into Derby's maven directory and
  
-    $ maven   # will attain the multiproject:install goal to install the artifacts into your
local maven repo
+    $ maven   # will attain the multiproject:install goal to install the artifacts into your
local maven repo. Note: For 10.3.2.1 I had to type maven multiproject:install to get this
to work.
  
     $ maven clean   # will attain the multiproject:clean goal to clean up the maven tree
  
@@ -477, +471 @@

  
    The deployment of the jars and poms to the Maven 1 repository will be automatically converted
to appropriate jars and poms for Maven 2 and deployed to that repository as well. See [http://issues.apache.org/jira/browse/DERBY-1378
DERBY-1378] for more information on the automatic conversion to Maven 2.
  
-   Maven may not work for you. If Maven does not copy the build artifacts to subdirectories
under /www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/, then you
will have to do this yourself. 
+   Maven may not work for you especially on Windows. If Maven does not copy the build artifacts
to subdirectories under /www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/,
then you will have to do this yourself. 
  
-   In this scenario, you must use Maven to deploy the build artifacts to your local file
system and then sftp the results to people.apache.org. To deploy the build artifacts to your
local file system, set up project.properties something like this:
+   In this scenario, you must use Maven to deploy the build artifacts to your local file
system, sign them and then sftp the results to people.apache.org. To deploy the build artifacts
to your local file system, set up project.properties something like this:
  
    {{{maven.repo.list=apache
  maven.repo.apache=file://~/zdir
@@ -494, +488 @@

  
     $ maven multiproject:deploy
  
+   This will build the artifacts into a subtree rooted at garbage. 
+   Sign the jars using the following script:
+   {{{
+    for i in `ls *.jar`
+    do
+      gpg --armor --detach-sign $i
+    done
+    }}}
+ 
-   This will build the artifacts into a subtree rooted at garbage. Use sftp to bulk put the
artifacts into the corresponding subdirectories of www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/.
+ Use sftp to bulk put the artifacts into the corresponding subdirectories of www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/.
  
   1. Update the Derby project DOAP file for an official release.
  
@@ -526, +529 @@

  
    Mark the release id as a released version in JIRA. To do this, go to the Administration
page, select Derby, then click the Manage versions link on the bottom right. Click the Release
link next to the version id of the release and add the release date. In addition, you may
need to create a new version id for the next release vehicle on the branch. The older development
versions used for tracking changes between releases are no longer needed, and old versions
should be merged into the release version. E.g. for the 10.3.1.4 release, 10.3.0.0, 10.3.1.0,
10.3.1.1, 10.3.1.2, and 10.3.1.3 need to be merged into the released 10.3.1.4. Click the Merge
button next to the oldest release. Select all the versions in the list on the right to merge
and then the released version to merge to on the left (in the example above, this would be
10.3.1.4), and click the Merge button and confirm the merge.
  
-  1. Announce the release.
- 
-   Twenty-four hours after putting the release files in the mirror directory, verify that
you can reach them through a mirror. Then, you should email derby-dev, derby-user, general@db.apache.org,
announce@apache.org and anyone else you think might be interested an announcement concerning
the release. See past release announcements for examples.
- 
-   Include a description of the project, and a description of any significant new features
or important bug fixes. 
- 
-   Every tech news blog remotely related to Java or databases will pick up the announcement
and post it verbatim, so it's a good idea to spell check it, proofread it a couple of times,
and/or get input from derby-dev on its content.
- 
-  1. Tag the release in subversion.
- 
-   {{{svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/code/{trunk_or_branchname}/

- 
- https://svn.apache.org/repos/asf/db/derby/code/tags/{version}/
- svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/docs/{trunk_or_branchname}/

- 
- https://svn.apache.org/repos/asf/db/derby/docs/tags/{version}/}}}
- 
   1. Update STATUS again.
  
    Update STATUS to reflect that the release has occurred. Check in the new file. 
  
-  1. Update the News section of the website.
- 
-   Update the News section at the bottom of the front page of the Derby website. Add the
announcement mail to the top of the news items at http://db.apache.org/derby/index.html#News

- 
-  1. Update JIRA versions and merge development versions into released version.
- 
  You're done!
- 
- 
  
  
  = Snapshots =

Mime
View raw message