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 "ReleasePrep" by RichardHillegas
Date Tue, 12 Oct 2010 19:03:43 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The "ReleasePrep" page has been changed by RichardHillegas.
http://wiki.apache.org/db-derby/ReleasePrep?action=diff&rev1=2&rev2=3

--------------------------------------------------

  
   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. <<Anchor(CutBranch)>>For major releases, create a new branch for the release,
in both the code and docs trees. See CreatingDerbyBranch
  
  ==== Work the toward a release candidate ====
  
@@ -182, +181 @@

  
   1. (Optional:) Have eclipse installed or make arrangements with someone willing to build
the eclipse ui plugin. As release manager you need to have access to the plugin zips if you
don't build them yourself (e.g. the volunteer can attach the plugin zips to a Jira issue).
<!> If you are not building the plugin yourself, make sure that the ''beta'' status
of the plugin matches that of the release candidate you are building.
  
+ ==== Create a New Branch ====
+ 
+ <<Anchor(CutBranch)>>For a major (feature) release, you must create a new branch
for the release, in both the code and docs trees. See CreatingDerbyBranch . Do this just before
you build the first release candidate.
+ 

Mime
View raw message