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 Thu, 01 May 2008 18:26:03 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

------------------------------------------------------------------------------
  
     {X} The build process frequently will create "false modifications" in `build/tmp` or
`build/site/skin`. These must be reverted before checking in the changes. 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]).
  
+    <!> Remember to svn add the new files and set `svn:executable` on the new CGI script
in `build/site/releases` after running forrest!
+ 
     {{{rm -rf $FORREST_HOME/main/site/*  # Remove any files from a previous build
  forrest site
  cp -r $FORREST_HOME/main/site build/site
  svn revert -R build/tmp build/site/skin
+ svn add build/site/releases/release-x.y.z.w.html
+ svn add build/site/releases/release-x.y.z.w.cgi
+ svn propset svn:executable ON build/site/releases/release-x.y.z.w.cgi
  }}}
  
    a. Check the changes. If they look good, 'svn commit' them.
@@ -569, +574 @@

  
   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.1.
+   {i} 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:
+   a. 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. 
  
+   a. 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.list=apache
  maven.repo.apache=scpexe://people.apache.org
  maven.repo.apache.directory=/www/www.apache.org/dist/java-repository
  maven.repo.apache.username={your_username}
  maven.repo.apache.password={your_password}
  maven.repo.apache.group=db}}}
  
-   Then, cd into Derby's maven directory and
+   a. Then, cd into Derby's maven directory and
  
-    $ 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   # 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
  
-    $ maven multiproject:deploy   # will copy all the artifacts into the apachecvs repository
(note, for now this has been disabled by commenting out the maven.repo.list definition in
project.properties).
+    $ maven multiproject:deploy   # will copy all the artifacts into the apachecvs repository
(note, for now this has been disabled by commenting out the maven.repo.list definition in
project.properties).}}}
  
-   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 that ant built into
jars/${sanity}.
  
-   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. 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.
  
-   {{{for i in *.jar
+    {{{for i in *.jar
  do
    gpg --armor --detach-sign $i   // enter your PGP passphrase for each iteration.
  done
@@ -603, +610 @@

    mv $i $NEWNAME
  done}}}
  
-   Then, upload the signatures to the jars directory:
+   a. Then, upload the signatures to the jars directory:
- 
-   {{{sftp {username}@svn.apache.org
+    {{{sftp {username}@svn.apache.org
  cd /www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/jars/
  put *.jar.asc}}}
  
-   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.
+   {i} 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 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. 
+  1. {X} 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, sign them and then sftp the results to people.apache.org.

+   a. 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.list=apache
  maven.repo.apache=file://~/zdir
  maven.repo.apache.directory=garbage
  maven.repo.apache.username=garbage
  maven.repo.apache.password=garbage
  maven.repo.apache.group=garbage}}}
  
-   Then do
+   a. Then do
  
     $ maven clean
  
     $ maven multiproject:deploy
  
-   This will build the artifacts into a subtree rooted at garbage. 
+    This will build the artifacts into a subtree rooted at garbage. 
+ 
-   Sign the jars using the following script:
+   a. Sign the jars using the following script:
-   {{{
+    {{{
     for i in `ls *.jar`
     do
       gpg --armor --detach-sign $i
     done
     }}}
  
-   Use sftp to bulk put the artifacts into the corresponding subdirectories of www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/.
+   a. 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.
+  1. Update the release section in the Derby project DOAP file for an official release.
+   {{{ cd site-trunk
+ vi doap_Derby.rdf
+ 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).

-     Update the release section in this file:
-     https://svn.apache.org/repos/asf/db/derby/site/trunk/doap_Derby.rdf
  
-    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). If
the update doesn't get generated within a day or two, send email to derby-dev@db.apache.org
letting them know you updated the file and that the update appears to be delayed (site-dev@apache.org
needs to be notified).
+   {X} If the update doesn't get generated within a day or two, send email to derby-dev@db.apache.org
letting them know you updated the file and that the update appears to be delayed (site-dev@apache.org
needs to be notified).
  
   1. Announce the release.
  

Mime
View raw message