ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Ws Wiki] Update of "Tuscany/TuscanyJava/SDOJavaReleaseSteps" by KelvinGoodson
Date Thu, 16 Nov 2006 14:14:01 GMT
Dear Wiki user,

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

The following page has been changed by KelvinGoodson:
http://wiki.apache.org/ws/Tuscany/TuscanyJava/SDOJavaReleaseSteps

------------------------------------------------------------------------------
    1. Make archives of your clean exports in order to be able to distribute source
    1. Follow the instructions in BUILDING.txt in the root folders of the source distributions
to produce the binary distribution
     1. If you have to do something different from those instructions to build the binary
distro, then update BUILDING.txt in appropriate places in svn(and be aware thet your source
distro archive is now out of date, so you'll need to iterate before going public)
+   1. Test your binary distro; take the outputs of your build process and use them as if
you were a new user who had just downloaded them
    1. create your sample programs source distribution
-    1. this is hacky at the moment and could be improved
     1. ...... fill this in
     1. ....
    1. At this point you will need to have put in place distro signing capabilities (see "Ahead
of Time" above)
@@ -73, +73 @@

   1. Update the tags version names of the dependencies to non SNAPSHOT versions, if not already
done earlier in the release candidate process
   1. Ideally update the tags version names of maven plugins to non SNAPSHOT versions if not
already done earlier in the release candidate process (note that if the plugin behaviour changes
after release, your tag or source distribution may not build in the same way as it did when
you released if you rely on SNAPSHOT plugin versions)
   1. Rebuild and upload a new release and candidate to people.apache.org
+  1. Optionally take a snapshot archive of your local maven repository for future issue resolution
   1. Deploy the projects artifacts to the maven repository
    1. By this time you want to have in place easy authentication to people.apache.org (add
link to apache description of how to do this),  and to modify your maven ~/.m2/settings.xml
file to use key based authentication, rather than password (I never got this going, so had
to type in my password about 30 times per deploy) -- If using pageant to make an ephermeral
decrypted version of your SSL private key available to the authentication process, then make
sure pageant is running, and you have lodged your private key with that invocation of pageant
    1. Run maven deploy (supplying your password multiple times if necessary -- the build
will fail if a password request times out)
@@ -92, +93 @@

   1. Momentarily reflect on life's joys
   
  
- 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org


Mime
View raw message