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 RichardHillegas
Date Tue, 27 Apr 2010 18:05:03 GMT
Dear Wiki user,

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

The "DerbySnapshotOrRelease" page has been changed by RichardHillegas.


   1. Keep the `jars/insane/*.jar` and `jars/insane/derby.war` files available. You will need
them for maven deployment after the vote is complete.
    (!) It is advisable to copy the jars to another directory and include the version number
of the release candidate in the directory name. This way you avoid having to extract the jars
from the release artifacts if you inadvertently overwrite the jars (through a rebuild) before
deploying to the maven repository.
-  1. <<Anchor(Bump4th)>>Bump the fourth digit of the source in preparation for
a possible next build:
+  1. <<Anchor(Bump4th)>>Bump the fourth digit of the source in preparation for
a possible next build. I don't think this step does anything except update the last digit
of the release id in release.properties. The bumped release id represents the head of the
  cd tools/release
@@ -414, +414 @@

    Commit the changed version number.
+  1. At the same time, make sure that that you add the bumped release id to JIRA. This allows
bugs to be marked as fixed at the head of the branch.
   1. Post the distributions
     a. Make sure the umask of your Apache account grants both read and write access to group
(db) and only read access to others. {i} Read access for others is necessary  for web access,
and the write permission for the db group will make life easier for future release managers.
     a. Create a new directory for the release candidate in your `people.apache.org:public_html`

View raw message