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, 26 Mar 2008 10:36:13 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

------------------------------------------------------------------------------
    * junit.jar 
   including those required for building the optional pieces:
    * The jdk1.6-specific classes (JDBC4 support)
-   * The OSGi support (osgi.jar or felix.jar. Felix.jar should be automatically present in
tools/java with 10.4 and later).
+   * The OSGi support (osgi.jar or felix.jar. felix.jar should be automatically present in
`tools/java` with 10.4 and later).
    * The JSR169 support
  
   1. [[Anchor(CopyPkgTmpl)]]Copy `tools/ant/properties/packaging.tmpl` to `tools/ant/properties/packaging.properties`
and modify as necessary.
@@ -189, +189 @@

  
    For information about PGP and why it is used to sign release binaries at Apache, please
read [http://people.apache.org/~henkp/trust/].
  
-   You should create a PGP key for yourself if you do not have one, and upload it to at least
one, preferably two, of the main public keyservers, e.g. pgp.mit.edu. You will need this key
to sign the release binaries. Your key should be tied into the Apache web of trust, which
means you should have at least one person sign your key, and you should have done gpg --refresh-keys
to get that person's signature before you follow the steps at the top of the KEYS file.
+   You should create a PGP key for yourself if you do not have one, and upload it to at least
one, preferably two, of the main public keyservers, e.g. pgp.mit.edu. You will need this key
to sign the release binaries. Your key should be tied into the Apache web of trust, which
means you should have at least one person sign your key, and you should have done `gpg --refresh-keys`
to get that person's signature before you follow the steps at the top of the KEYS file.
  
    GPG is available for a variety of platforms from http://gnupg.org. PGP is a commercial
product which is available from http://pgp.com.
  
@@ -215, +215 @@

  === For the first release candidate on a new branch ===
  
   1. Update `tools/ant/properties/release.properties` by hand, and set the `beta` property
to false.
-  1. Create `maintversion.properties`, by running:
-   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties

- tools/release/maintversion.properties}}}
-   This step will ''not'' modify any files under version control, but you will need the unversioned
`maintversion.properties` when you [#CreateDistros create the distributions] later on. '''
/!\ Is this really true? Seems like this is done automagically when building the release artifacts?'''
   1. Check in the modification.
   1. You will need to clobber and build again before you can see the changed `beta` property
reflected in the source. Note that the first release off a new branch is automatically beta,
even if you set the `beta` property to false.
  
@@ -232, +228 @@

  The third and fourth parts of the version number are combined into a single property, maint,
where maint = (third digit * 1000000) + fourth digit. Note that removing the beta flag will
not have an effect unless the 3rd digit (fixpack) is greater than 0, since version numbers
with fixpack=0 always are considered alpha. Fixpack (3rd digit) will normally be set to 1
when the [#BranchCutting branch is cut], but if it isn't, it must be incremented before the
release candidate can be created. 
  
  ==== Check-ins just before generating release artifacts ====
- 
- /!\ '''Check in the new version number after RC is spun?''' 
  
   1. Also adjust version numbers in documentation by modifying the appropriate `*conrefs.dita`
files.
  
@@ -261, +255 @@

  	- RELEASE_NOTES and CHANGES (''only for version < 10.3'') checked in
  
  	- md5 & pgp and docs info set correctly in `tools/ant/properties/packaging.properties`
and available (PATH)
- 
- 	- generated updated `tools/release/maintversion.properties` ( /!\ ''' Is it still required?''')
  
  	- `ant.properties` set correctly for: jdk15, jdk16, jsr169
  
@@ -352, +344 @@

  
    Keep the `jars/insane/*.jar` files available. You will need them for maven deployment
after the vote is complete.
  
-  1. [[Anchor(Bump4th)]]Bump the fourth digit of the source in preparation for a possible
next build
+  1. [[Anchor(Bump4th)]]Bump the fourth digit of the source in preparation for a possible
next build:
-   You should update tools/ant/properties/release.properties by hand and then run:
- 
-   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties
tools/release/maintversion.properties
- }}}
- 
-   /!\ '''Is this still necessary?'''
  
    {{{cd tools/release
  ant bumplastdigit}}}
  
-   /!\ '''Commit the changed version number here?'''
+   Commit the changed version number.
    
   
   1. Post the distributions

Mime
View raw message