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 "ReleaseCandidates" by BryanPendleton
Date Tue, 11 Oct 2016 01:01:27 GMT
Dear Wiki user,

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

The "ReleaseCandidates" page has been changed by BryanPendleton:
https://wiki.apache.org/db-derby/ReleaseCandidates?action=diff&rev1=4&rev2=5

  
    'svn up' in your subversion view to bring all files in your view up to the latest revision.
Otherwise, the version output by svn which is captured for the build number will be a range
(e.g. 290275:320938).
  
+ ==== Verify your machine configuration ====
- ==== Build the release artifacts ====
- 
- You may skip this section too if you are building a 10.7 or later release. The work described
in this section is performed by the master "release" target in the top level 10.7 build.xml
file. for 10.7 or later, all you have to do is invoke the "release" target and answer the
questions it poses.
  
   1. Check you have all required pieces:
  	- doc tree
@@ -74, +72 @@

  	  - with latest SQLState
  	- `KEYS` checked in
  
- 	- `RELEASE_NOTES.html` and CHANGES (''only for version < 10.3'') checked in.
+ 	- `RELEASE_NOTES.html` (and, ''only for version < 10.3'', CHANGES) checked in.
  
- 	- md5 & pgp and docs info set correctly in `tools/ant/properties/packaging.properties`
and available (PATH)
+ 	- md5 & pgp and docs info set correctly in `~/ant.properties` or in `tools/ant/properties/packaging.properties`
and available (PATH)
  
- 	- `ant.properties` set correctly for: jdk15, jdk16, jsr169
+ 	- (''for version < 10.13'') `~/ant.properties` set correctly for: jdk15, jdk16, jsr169
  
  	- sane not set in `ant.properties`
  
  	- non-source files for building source available: `junit.jar`, `felix.jar`, (with 10.3
and earlier: `osgi.jar`), dita library (again).
   
+ ==== Build the release artifacts ====
+ 
+ You may skip this section too if you are building a 10.7 or later release. 
+ 
+ The work described in this section is performed by the master "release" target in the top
level 10.7 build.xml file. for 10.7 or later, all you have to do is invoke the "release" target
and answer the questions it poses.
+ 
   1. Build the documentation.
  
    The documentation needs to be included in the -bin distribution and src, so you will need
to access the doc branch when running the ant release target. The doc build is not controlled
by the source tree build, and thus needs to be completed beforehand.

Mime
View raw message