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 13:00:39 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

------------------------------------------------------------------------------
    {{{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}/
-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, 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:
+ 
+  1. 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 so you need to edit `tools/ant/properties/release.properties`
on trunk by hand. Bump the major/minor properties as appropriate, zero out the maint property
(if it isn't zero already), and ensure the beta flag is set to true (if it isn't already):
  
    {{{vi tools/ant/properties/release.properties
  }}}
+ 
+   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.
+ 
-   Then, you can use the `bumplastdigit` ant target to set the `maint` property. This target
is only available in the `tools/release` directory:
+  1. Then, '''on the new branch''', 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.
+ 
+   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 do a clean build (`ant clobber;
ant all`) and run some or all tests before committing this change to the branch.
  
   1. Post to derby-dev requesting that a new version be added to JIRA for the next version
of Derby (this may well have been done earlier).
  
@@ -76, +81 @@

  
    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. (Unless you have already done so. It may be convenient
to have a 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.
-  1. Create wiki pages for the release. (Unless you have already done so. It may be convenient
to have a 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.
  
  ==== Work the toward a release candidate ====
  

Mime
View raw message