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 Tue, 29 Apr 2008 16:18: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

------------------------------------------------------------------------------
  
    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 new versions be added to JIRA for the beta version
on the branch and the new development version of Derby on trunk (this may well have been done
earlier). /!\ '''This is [#VersionInJIRA the first item of the next section]?'''
- 
   1. 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`. For a
minor (bug fix) release, consider bumping the third version of the source tree it will come
off (likely a branch).
  
  
  ==== Work the toward a release candidate ====
  
-  1. [[Anchor(VersionInJIRA)]]Arrange for the version in JIRA; See section titled 'JIRA version
maintenance'. /!\ '''There is no such section in this page? Overlaps with item in previous
section?''' -dt /!\
+  1. [[Anchor(VersionInJIRA)]] Arrange for the version in JIRA. Unless you are a Jira-admin
you need to post to derby-dev requesting that new versions be added to JIRA. For any release
you need a new version for the (beta) release candidate. When creating a new branch you also
need a new development version for trunk, (unless this has been done earlier for some reason).
  
   1. Target the bugs you feel should be fixed in JIRA
  

Mime
View raw message