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 "ReleasePrep" by RichardHillegas
Date Tue, 12 Oct 2010 19:21:43 GMT
Dear Wiki user,

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

The "ReleasePrep" page has been changed by RichardHillegas.
http://wiki.apache.org/db-derby/ReleasePrep?action=diff&rev1=5&rev2=6

--------------------------------------------------

    * volunteer for release manager and announce this
    * create wiki pages (main, buddytesting, platform testing, app testing) for release
    * troll for buddies for buddytesting
-   * (optional:) create branch
    * ensure you have all required tools and files 
    * ensure your KEYS are in place, and signed
-   * create `packaging.properties` based on `packaging.tmpl`
+   * (for 10.6 or older branches) create `packaging.properties` based on `packaging.tmpl`
+   * (optional:) create branch
  
  === Before a candidate can be generated ===
  
@@ -80, +80 @@

  
  To be able to produce the release artifacts, you need to
    * update version numbers and run tests to verify it was correct
-   * generate release notes and `CHANGES.html`
-   * build all in doc and source objects (except for eclipse ui and doc plugins, those are
optional)
+   * generate release notes
+   * build all in doc and source objects (except for the eclipse ui plugin, which an eclipse-savvy
developer can create for you)
    * sign 
    * verify
  and after the release has been voted on:
@@ -108, +108 @@

    * osgi support (for 10.3 and earlier `osgi.jar` - see: `BUILDING.txt` for your version.
10.4 and later always builds this using `tools/java/felix.jar`)
  
  You need to at least have the doc tree and source tree available, and your `ant.properties`
file needs to include:
+ {{{
  proceed=true
  relnotes.src.reports=<location where you want to save/access the xml scripts for generating
release notes>
+ docs.root=<location of the root directory of your docs client>
  #sane=<sane should *not* be set>}}}
  
  For 10.4 and earlier, your `ant.properties` file also needs to include:
@@ -121, +123 @@

  {i} Special consideration for non-linux users:
   {X} [[#CopyPkgTmpl|ant sign]], the last step in the ant release process, may not work.
<!> Try it out before the release time arrives!
  
-  {X} Your md5 tool may be different. You will most likely need to [[#CopyPkgTmpl|configure
the ant sign target for your system]]. {i} You do this by copying `packaging.tmpl` to `packaging.properties`
and adjust it appropriately for your system.
+  {X} Your md5 tool may be different. You may need to [[#CopyPkgTmpl|configure the ant sign
target for your system]]. {i} For 10.6 and earlier, you this by copying `packaging.tmpl` to
`packaging.properties` and adjusting it appropriately for your system. For 10.7 and later,
you provide appropriate overrides for the following properties. The default values of these
properties are found in packaging.tmpl and you put your overrides in ant.properties:
+ 
+ {{{
+ md5.exec=<name of your checksumming executable>
+ md5.options=<options to be passed on the command line to the checksumming executable>
+ pgp.exec=<name of your signing executable>
+ pgp.options=<options to be passed on the command line to the signing executable>}}}
  
   (!) If you cannot do this, you may achieve the same using [[#SignOne|this script]]. 
  

Mime
View raw message