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 Mon, 10 Mar 2008 10:55:04 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

------------------------------------------------------------------------------
  
   1. For major releases, create a new branch for the release, in both the code and docs trees.
  
-   {{{svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/code/trunk/ https://svn.apache.org/repos/asf/db/derby/code/branches/{branchname}/
+   {{{svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/code/trunk/ https://svn.apache.org/repos/asf/db/derby/code/branches/{branchname}/
-m "Created the {branchname} source branch"
- 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}/}}}
+ 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}/
-m "Created the {branchname} doc branch}}}
  
-   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/properties/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:
+   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, but there is one to update the
`maint` property. Hence, you need to edit `tools/ant/properties/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:
  
-   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties

- tools/release/maintversion.properties}}}
+   {{{vi tools/ant/properties/release.properties
+ }}}
+   Then, you can use the `bumplastdigit` ant target to set the `maint` property. This target
is only available in the `tools/release` directory:
+ 
+   {{{cd tools/release 
+ ant bumplastdigit}}}
+   If you look at `tools/ant/properties/release.properties` again you should see that the
`maint` property has been updated. It is probably a good idea to update to the head of trunk,
and do a clean build (`ant clobber; ant all`) and run some or all tests before committing
the change.
  
    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]
+   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`.
-  The actual page to modify is src\documentation\content\xdocs\dev\derby_source.xml.
  
    For a minor (bug fix) release, consider bumping the third version of the source tree it
will come off (likely a branch).
  
-  1. Create wiki pages for the release.
+  1. Create wiki pages for the release. (Unless you have already done so. I may be convenient
to have the Wiki page prior to feature freeze and branch cutting).
  
    Use pages for a previous release as a template. You're likely to create a general page
and a page to hold the testing information.
  

Mime
View raw message