lucene-java-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-java Wiki] Update of "ReleaseTodo" by SteveRowe
Date Fri, 25 Jan 2013 07:14:41 GMT
Dear Wiki user,

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

The "ReleaseTodo" page has been changed by SteveRowe:
http://wiki.apache.org/lucene-java/ReleaseTodo?action=diff&rev1=137&rev2=138

Comment:
Modernize

  <<TableOfContents>>
  
  = Release Process =
+ 
  Prior to every major or minor release (i.e. all except bugfix-only point releases) a feature
freeze phase takes place for about 1-2 weeks. At the beginning of the feature freeze the trunk
is branched and no commits other than serious bug fixes, documentation or build updates are
permitted. This period of time should be used for extensive testing, documentation improvements
and for cleaning up old JIRA issues.
  
  = Prerequisites =
@@ -12, +13 @@

   1. You may need to setup people.apache.org as a known host for ssh if you haven't already.
 This happens when you log in manually and follow the prompts.
  
  = Planning =
- On dev@lucene.apache.org, decide on
+  1. On dev@lucene.apache.org, decide on
- 
-  1. which JIRA issues shall be committed before a release is made; set the appropriate "Fix
Version" in JIRA for these issues
+     a. which JIRA issues shall be committed before a release is made; set the appropriate
"Fix Version" in JIRA for these issues
-  1. the date for branching the trunk and the start of the feature freeze phase
+     a. the date for branching the trunk and the start of the feature freeze phase
-  1. the length of the feature freeze phase
+     a. the length of the feature freeze phase
-  1. a tentative release date
+     a. a tentative release date
+  1. Put up (and/or fix up existing) release notes, at http://wiki.apache.org/lucene-java/ReleaseNoteXY
and http://wiki.apache.org/solr/ReleaseNoteXY and ask on dev@ for input
  
  = Branching & Feature Freeze =
+ 
   1. Run {{{ant precommit}}} to run a bunch of sanity & quality checks, then fix any
problems that are found.
   1. For the first release in a minor release series - i.e. X.Y.0 - create a minor release
branch off the current major version branch, e.g. for minor release 4.2:
   {{{
@@ -86, +88 @@

  }}}
  
  = Testing the Release artifacts =
+ 
   1. There is a script in SVN to do automated checks on a release candidate, e.g {{{python3.2
-u dev-tools/scripts/smokeTestRelease.py http://people.apache.org/~whoever/3.7.0rc1-rev1384901
3.7.0 tmp}}} 
  
  = Publishing =
@@ -96, +99 @@

  svn copy https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_X_Y \
  https://svn.apache.org/repos/asf/lucene/java/tags/lucene_solr_X_Y_Z -m "Lucene Java X.Y.Z
release."
  }}}
+ 
   1. If this is a point release, copy the CHANGES.txt entry for this point release back to
the trunk's CHANGES.txt. Remove any duplicate entries from trunk's CHANGES.txt (ie, each issue
should appear only once, in the earliest point-release that contains the fix, on the assumption
that all future releases also contain the fix).
+  1. Add the new releases to svnpubsub:
+     a. Check out the Lucene PMC svnpubsub release area:
+     {{{
+        svn co https://dist.apache.org/repos/dist/release/lucene/ dist/release/lucene
+ }}}
+     a. Make a directory for the new release under {{{lucene/java/}}} and {{{lucene/solr/}}}.
+     a. Copy the successfully voted RC to {{{dist/release/lucene/java/}}} and {{{dist/release/lucene/solr/}}},
excluding the {{{maven/}}} directories.
+     a. Commit the relesase candidate.
   1. [[PublishMavenArtifacts|Publish Maven Artifacts]]
-  1. Wait 24 hours to give the mirrors a chance to get the new release.  There is a script
that will continually check the number of mirrors (and Maven Central) that have the release
for you: {{{dev-tools/scripts/poll-mirrors.pl}}}.
+  1. Wait 24 hours to give the mirrors a chance to get the new release.  There is a script
that will continually check the number and percentage of mirrors (and Maven Central) that
have the release: {{{dev-tools/scripts/poll-mirrors.pl}}}.
  
  = Pushing website changes & Announcing =
  
@@ -148, +160 @@

   1. update the core & solr doap.rdf files to reflect the new versions using the Apache
CMS
      * https://cms.apache.org/redirect?uri=http://lucene.apache.org/core/doap.rdf
      * https://cms.apache.org/redirect?uri=http://lucene.apache.org/solr/doap.rdf
+  1. Publish the site, e.g. by visiting http://lucene.staging.apache.org, invoking the [xhttps://cms.apache.org/#bookmark|CMS
bookmarklet], then clicking the publish link.
   1. Wait for these changes to appear on Apache's main webserver (http://lucene.apache.org)
before doing the next steps (see http://www.apache.org/dev/project-site.html for details on
how the site is mirrored to Apache's main web servers). Once they appear, verify all links
are correct in your changes!
  
  == Announce the release ==
+  1. Announce the release on general@lucene.apache.org , dev@lucene.apache.org , java-user@lucene.apache.org
and announce@apache.org mailing lists. A draft should be sent to the development list first
to clarify any possible issues in the announcement.  Make sure the announcement has a brief
blurb at the top saying what Lucene is (it will save you several snarky comments in reply.)
Mails to the announce list should be sent from an @apache.org email address and contain a
signature.  Release announcements can be shared/edited on the wiki at http://wiki.apache.org/lucene-java/ReleaseNoteXY
and http://wiki.apache.org/solr/ReleaseNoteXY, or in https://svn.apache.org/repos/asf/lucene/dev/misc/announcements.
   1. Add the new version to Wikipedia (english and maybe your own language)
   1. Add the new release to https://freecode.com/ (formerly freshmeat.com)
-  1. Announce the release on general@lucene.apache.org , dev@lucene.apache.org , java-user@lucene.apache.org
and announce@apache.org mailing lists. A draft should be sent to the development list first
to clarify any possible issues in the announcement.  Make sure the announcement has a brief
blurb at the top saying what Lucene is (it will save you several snarky comments in reply.)
Mails to the announce list should be sent from an @apache.org email address and contain a
signature.  Release announcements can be shared/edited in https://svn.apache.org/repos/asf/lucene/dev/misc/announcements.
  
  == Update JIRA ==
   1. Go to the JIRA "Manage Versions" Administration page (http://issues.apache.org/jira/secure/project/ManageVersions.jspa?pid=12310110)
and click Release for the version you just released. Also add a new (unreleased) version for
the next release on the trunk (for a major release) or branch (for a minor release).

Mime
View raw message