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 Fri, 02 May 2008 13:39:12 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

------------------------------------------------------------------------------
  
     {i} As of this writing, the latest 1.x version of Maven was 1.1.
  
-   a. `cd` into Derby's `maven` directory. {i} Typically this will be in the same sandbox
that you used to build the release, but this is not strictly required.
+   a. `cd` into Derby's `maven` directory. Typically this will be in the same sandbox that
you used to build the release, but this is not strictly required.
  
    a. Edit `project.xml` so that it contains the correct version number for this release
between the <currentversion> tags. 
  
@@ -603, +603 @@

   maven.repo.apache.group=db}}}
  
    a. Run the Maven commands. 
-    * cd into Derby's maven directory
     * Run `maven` to attain the `multiproject:install` goal to install the artifacts into
your local maven repo.
+ 
-    {X} Note: For 10.3.2.1 I had to type `maven multiproject:install` to get this to work.
+     {X} Note: For 10.3.2.1 I had to type `maven multiproject:install` to get this to work.
+ 
     * Run `maven clean` to attain the `multiproject:clean` goal to clean up the maven tree.
     * Run `maven multiproject:deploy` to copy all the artifacts into the apachecvs repository.
  
-    {X} The checked in version of `project.properties` disables this step by commenting out
the `maven.repo.list` property.
+    <!> The `multiproject:deploy` command will not work unelss you uncomment the `maven.repo.list`
property in `project.properties`.
  
-    {{{cd maven
- maven
- [...lots of output...]
- maven clean
- [...lots of output...]
- maven multiproject:deploy
- [...lots of output...]}}}
- 
-    {i} This does not build using maven, it works by copying the jars that ant built into
jars/${sanity}.
+    {i} This does not build using maven, it works by copying the jars pointed to by `${derby.jars}`
(`jars/${sanity}` by default).
  
-   a. After successfully deploying the jars to the maven repository on minotaur, you may
receive an email that you did not upload appropriate PGP signatures for the new files added
to www.apache.org/dist/. To prevent receiving this mail, you will need to sign the individual
jars and then upload the signatures to `/www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/jars`
after running maven's `multiproject:deploy` target. The following script signs and renames
the jars appropriately, and should be run in the `jars/insane` directory.
+   a. Sign the individual jars. 
+    Unfortunately, Maven renames the jars during deployment, so the jars now found in the
Maven repository have the version number embedded in the file name. E.g `derby.jar` has become
`derby-x.y.z.w.jar`. The name of the signature file needs to same as the name of jar with
the `asc` extension, but Maven apparently knows nothing about signatures, so we have to create
correctly named signatures by hand. The following script signs and renames the jars appropriately,
and should be run in the `${derby.jars}` directory. 
  
     {{{for i in *.jar
  do
@@ -630, +624 @@

  for i in *.jar.asc
  do
    PREFIX=`echo $i | sed 's/.jar.asc//g'`
-   NEWNAME=$PREFIX-10.1.2.1.jar.asc   //use the correct version number for this release.
+   NEWNAME=$PREFIX-x.y.z.w.jar.asc   //use the correct version number for this release.
    mv $i $NEWNAME
  done}}}
  
-   a. Then, upload the signatures to the jars directory:
+   a. Upload the signatures to the jars directory:
     {{{sftp {username}@svn.apache.org
  cd /www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/jars/
  put *.jar.asc}}}
+ 
+    {i} If you don't upload the signatures for the jar files, you will probably receive an
email saying that you did not upload appropriate PGP signatures for the new files added to
`www.apache.org/dist/`.
  
    a. Revert local modifications in the `maven` directory.
  
@@ -674, +670 @@

   1. Update the release section in the Derby project DOAP file for an official release.
    {{{ cd site-trunk
  vi doap_Derby.rdf
- svn commit
+ svn commit}}}
- ssh you@people.apache.org
- cd /www/db.apache.org/derby
- svn up }}}
  
    {i} This DOAP file is the source for http://projects.apache.org/projects/derby.html .
Projects are supposed to get updated periodically (you don't do anything to publish the update).

  
@@ -687, +680 @@

  
    Twenty-four hours after putting the release files in the mirror directory, verify that
you can reach them through a mirror (the mirroring will likely take effect long before this).
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.
  
-   <!> Note that you can only send emails to announce@apache.org from Apache account!
+   <!> Note that you can only send emails to announce@apache.org from your Apache account!
  
    Include a description of the project, and a description of any significant new features
or important bug fixes. 
  
@@ -695, +688 @@

  
   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/code/branches/{version}/
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}/}}}
+ svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/docs/branches/{version}/ https://svn.apache.org/repos/asf/db/derby/docs/tags/{version}/}}}
  
   1. Check in a copy of the jars to the jars directory of the repository.
  

Mime
View raw message