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 Wed, 30 Apr 2008 09:36:54 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. 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).
+  1. Add the new branch number to the list of branches on the source page of the website.

+   {i} 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. 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. [[Anchor(VersionInJIRA)]] Arrange for the new version(s) 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
  
    All features and bug fixes should be tracked in JIRA: http://issues.apache.org/jira/browse/DERBY
-   Mark the Fix In field for the JIRA entries for the items you want to be in the release
with the proper version. Also, it's a good idea to post to derby-dev to get an idea of what
features or fixes other contributors would like in the release.
  
+   Mark the Fix In field for the JIRA entries for the items you want to be in the release
with the proper version. 
+ 
+   (!) Also, it's a good idea to post to derby-dev to get an idea of what features or fixes
other contributors would like in the release.
+ 
-  1. Fix the bugs, update STATUS and CHANGES/RELEASE_NOTES.html as needed
+  1. Fix bugs and update `STATUS` (and `CHANGES.html`/`RELEASE_NOTES.html` as needed)
  
-   Get to work! Add features, fix bugs, and update STATUS as you go. The wiki is nice, as
are personal webpages, but STATUS is the designated place for Apache projects to keep their
current status. Apache members and committers expect to be able to grab the STATUS file from
the code tree to determine the current status of the project. It's a nice thing to keep the
STATUS file on branches up to date with the current status of the branch. The other essential
document is a document describing the changes. Derby branches up to 10.2 included a file 'CHANGES'
for that purpose; 10.3 branch and trunk have a RELEASE_NOTES.html checked in. RELEASE_NOTES.html
is generated using the generator in <10.3 branch and up/trunk>/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java,
which is activated by executing ant genrelnotes in tools/release. The CHANGES.html file can
be generated using <10.3 branch and /trunk>/java/build/org/apache/derbyBuild/ChangesFileGenerator.java,
which can be
  activated using ant genchanges in tools/release.
+   Get to work! Add features, fix bugs, and update STATUS as you go. The wiki is nice, as
are personal webpages, but `STATUS` is the designated place for Apache projects to keep their
current status. Apache members and committers expect to be able to grab the `STATUS` file
from the code tree to determine the current status of the project. 
+ 
+   (!) It's a nice thing to keep the STATUS file on branches up to date with the current
status of the branch. 
+ 
+   {i} Derby branches up to 10.2 included a file `CHANGES` for that purpose; 10.3 branch
and trunk have `RELEASE_NOTES.html` checked in and `CHANGES.html` which is generated for the
release. The process of generating these files is described at the ReleaseNoteProcess wiki
page.
  
   1. [[Anchor(DriveBugListToZero)]] Drive the bug list to zero.
  
    As the list of remaining bugs in JIRA approaches zero, be sure to mark their status properly
in JIRA. Mark blocker and critical bugs as such so that others can see the status at a glance.
Move non-showstopper bugs out to future releases if it appears they will not be fixed for
this release.
  
   1. Drive the creation of release notes.
-   The release note generator expects files called 'ReleaseNote.html' for each item marked
that is:
+   The release note generator expects files called `ReleaseNote.html` for each item marked
that is:
      * resolved to 'Fixed'
      * fixed in the release under study but not in the previous release
      * marked with 'Existing Application Impact' or 'Release Note Needed'.
+   {i} More info can be found at ReleaseNoteProcess.
  
-  1. Check that all creative works have ASF license headers. See: [http://wiki.apache.org/db-derby/FixingLicenseHeader].
+  1. Check that all creative works have ASF license headers. 
+   {i} See: [http://wiki.apache.org/db-derby/FixingLicenseHeader].
  
   1. Check that the year and other information is correct.
  
+   Ensure that the year in `NOTICE` is correct.
+ 
-   Ensure that the year in NOTICE is correct. Ensure that all versions and copyright details
in the docs tree are correct, this includes the top level conrefs.dita, as well as lower level
dita files.
+   <!> Ensure that all versions and copyright details in the docs tree are correct,
this includes the top level `conrefs.dita`, as well as lower level dita files.
+ 
  
  ==== Environment requirements for the release manager ====
  

Mime
View raw message