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 Wed, 30 Apr 2008 10:38:56 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

------------------------------------------------------------------------------
  
  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
+   * generate release notes and `CHANGES.html`
    * build all in doc and source objects (except for eclipse ui and doc plugins, those are
optional)
    * sign 
    * verify
@@ -147, +147 @@

    * modify derby web
    * distribute to maven
  
- This means you have to have to be able to do the following / use the following tools:
+ This means you have to have to be able to do the following / use the following tools ( {i}
see: `BUILDING.txt`):
-   * md5 (aka. `md5sum` or `digest -a md5`. See also how to [#CopyPkgTmpl configure `ant
sign`])
+   * md5 {X} The tool for generating md5 sums varies between systems. You may have to use
`md5sum` or `digest -a md5`. {i} See also how to configure the [#CopyPkgTmpl ant sign target])
-   * pgp (see: [http://people.apache.org/~henkp/trust/], [http://gnupg.org] or [http://pgp.com.]
)
+   * pgp ( {i} see: [http://people.apache.org/~henkp/trust/], [http://gnupg.org] or [http://pgp.com.]
)
-   * ant (see BUILDING.txt)
+   * ant
-   * dita (see: [http://db.apache.org/derby/manuals/dita.html] )
+   * dita ( {i} see: [http://db.apache.org/derby/manuals/dita.html] )
-   * forrest (see: [http://db.apache.org/derby/papers/derby_web.html] )
+   * forrest ( {i} see: [http://db.apache.org/derby/papers/derby_web.html] )
-   * eclipse (optional)
+   * eclipse (optional:)
  
- And you have to have the following files available:
+ And you have to have the following files available ( {i} see: `BUILDING.txt`):
-   * 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)
+   * 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`)
-   * j2me implementation (see BUILDING.txt)
-   * jdk16 implementaion (see BUILDING.txt)
-   * junit.jar (see BUILDING.txt)
+   * j2me implementation
+   * jdk16 implementaion
+   * junit.jar
-   * DITA-OT1.1.2.1_bin-ASL.zip (see: [http://db.apache.org/derby/manuals/dita.html])
+   * `DITA-OT1.1.2.1_bin-ASL.zip` ( {i} see: [http://db.apache.org/derby/manuals/dita.html])
  
- You need to at least have the doc tree and source tree available, and your ant.properties
file needs to include:
+ You need to at least have the doc tree and source tree available, and your `ant.properties`
file needs to include:
  {{{j14lib=<location of jdk14(2)/jre/lib>
  jdk16=<location of jdk16>
  jsr169compile.classpath=<location of jsr169 implementation>
@@ -172, +172 @@

  relnotes.src.reports=<location where you want to save/access the xml scripts for generating
release notes>
  #sane=<sane should *not* be set>}}}
  
- Special consideration for non-linux users:
+ {i} Special consideration for non-linux users:
-   * [#CopyPkgTmpl ant sign], the last step in the ant release process, may not work. Try
it out before the release time is there; if you cannot do this, you may achieve the same using
[#SignOne this script]. 
-   * Similarly, you may use a script to verify the release
-   * Your md5 tool may be different. You'll need to [#CopyPkgTmpl copy the file packaging.tmpl
to packaging.properties and adjust it appropriately].
+  {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.
+ 
+  (!) If you cannot do this, you may achieve the same using [#SignOne this script]. 
  
  ==== Steps to prepare your machine/code check-out for the release process ====
  

Mime
View raw message