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 MyrnavanLunteren
Date Mon, 04 Feb 2008 23:00:49 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 MyrnavanLunteren:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

------------------------------------------------------------------------------
    * build all, then: 
    * update release.properties
    * create maintversion.properties
-   * update masters (ant regex) and test
    * ensure all release notes are current
    * copy rrefexcept.dita from <source>/classes/doc to <docsource>/src/ref
    * update releaseSummary.xml, create release notes & changes files
@@ -62, +61 @@

  svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/docs/trunk/ https://svn.apache.org/repos/asf/db/derby/docs/branches/{branchname}/}}}
  
    After creating the branch, bump the version number on the trunk. There is not currently
an ant target for bumping the version number on the trunk. You should edit tools/ant/release.properties
on trunk by hand to bump the major/minor properties as appropriate, zero out the maint property,
and ensure the beta flag is set to true. Then, from the top, run:
+ 
-   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties
tools/release/maintversion.properties}}}
+   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties

-   {{{cd tools/release
- ant regex.masters}}}
-   Note: the regex.masters target does not currently account for changes in the beta flag.
Run the tests to make sure  the output files are correct. Don't forget to post to derby-dev
requesting that a new version be added to JIRA for the next version of Derby.
+ tools/release/maintversion.properties}}}
+ 
+   Don't forget to post to derby-dev requesting that a new version be added to JIRA for the
next version of Derby.
  
    Add the new branch number to the list of Branches on the source page of the website. For
instructions on how to build the website using Forrest, please see: [http://db.apache.org/derby/papers/derby_web.html]
   The actual page to modify is src\documentation\content\xdocs\dev\derby_source.xml.
@@ -204, +204 @@

  
  ==== Check-ins just before generating release artifacts ====
  
-  1. Bump the version number, adjust the beta flag and check in the new version and test
masters. 
+  1. Bump the version number, adjust the beta flag and check in the new version. 
  
    The third and fourth parts of the version are combined into a single property, maint,
where maint = (third digit * 1000000) + fourth digit. Also, if this is a major/minor (feature)
release, you should remove the beta flag at this time. 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
+   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties

+ tools/release/maintversion.properties}}}
- cd tools/release
- ant regex.masters}}}
-   Note: the regex.masters target does not currently account for changes in the beta flag.

  
    You will need to clobber and build again before you can see the changed release number(s)
reflected in the source. Note that the first release off a new branch is automatically beta,
even if you set the beta flag in tools/ant/properties/release.properties to false. Also adjust
version numbers in documentation by modifying the appropriate *conrefs.dita files.
- 
-   It's a good idea to build, then run at least one of the affected tests to make sure they
pass, before checking in the changed masters.
  
   1. Generate RELEASE_NOTES.html in the branch and check it into the svn repository.
  
@@ -241, +237 @@

  	- RELEASE_NOTES and CHANGES checked in
  	- md5 & pgp and docs info set correctly in tools/ant/properties/packaging.properties
and available (PATH)
  	- generated updated tools/release/maintversion.properties
- 	- updated masters checked in
  	- ant.properties set correctly for:
  		osgi.jar(10.3 and earlier), jdk15, jdk16, jsr169
  	- sane not set in ant.properties
@@ -328, +323 @@

  
  Keep the jars/insane/*.jar files available. You will need them for maven deployment after
the vote is complete.
  
-  1. Bump the fourth digit of the source in preparation for a possible next build; update
the masters
+  1. 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
+   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties
tools/release/maintversion.properties}}}
- cd tools/release
- ant regex.masters}}}
  
   1. Post the distributions
  

Mime
View raw message