lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "HowToReleaseSlowly" by SteveRowe
Date Sun, 13 Mar 2011 05:38:27 GMT
Dear Wiki user,

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

The "HowToReleaseSlowly" page has been changed by SteveRowe.
The comment on this change is: -dev -> -SNAPSHOT; drop maven_release; solr-dev@ -> dev@.
http://wiki.apache.org/solr/HowToReleaseSlowly?action=diff&rev1=66&rev2=67

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

   * The Maven Ant tasks in your Ant Home lib directory: http://maven.apache.org/download.html#Maven_Ant_Tasks
  
  = Release Planning =
- Start a discussion on solr-dev about having a release, questions to bring up...
+ Start a discussion on dev@ about having a release, questions to bring up...
  
   * Any unresolved Jira issues with the upcoming version number listed as the "Fix Version"
   * Any [[https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310230&fixfor=-1&resolution=1&sorter/field=issuekey&sorter/order=DESC&sorter/field=updated&sorter/order=DESC|"Fixed"
Jira issues missing a "Fix Version"]] that should be updated to indicate that there were fixed
in this upcoming version
@@ -33, +33 @@

   1. Check that Solr works on the latest versions of Jetty, Tomcat, and Resin.
   1. Double Check that there are no remaining unresolved Jira issues with the upcoming version
number listed as the "Fix" version
   1. Double Check that there are no [[https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310230&fixfor=-1&resolution=1&sorter/field=issuekey&sorter/order=DESC&sorter/field=updated&sorter/order=DESC|"Fixed"
Jira issues missing a "Fix Version"]] that should be marked as fixed in this release.
-  1. Make sure the src/maven artifact templates are in sync with the dependencies in the
Ant build file.
   1. Make sure the Ant sign-artifacts target is in sync with all of the artifacts that are
created.  All released artifacts must be signed.
   1. Is your Key in the KEYS file?
  
@@ -54, +53 @@

    . '''Note:''' at the moment releases need to be done on a unix box or in a cygwin environment
with unix linefeeds, because fixcrlf is only done on the sources in the zip artifact
   1. Update the version numbers in common-build.xml on the branch:
    * specversion should be set to X.Y.M.${dateversion}, where X.Y.M is the release being
made.
-   * version should be set to X.Y.N-dev, where N is one greater than the release being made.
-   * maven_version should be set to X.Y.N-SNAPSHOT, where N is one greater than the release
being made.
+   * version should be set to X.Y.N-SNAPSHOT, where N is one greater than the release being
made.
   1. commit the changes to both trunk and branch
   1. On the branch, compile the code and run unit tests.
-   . {{{ant -Dversion=X.Y.M -Dspecversion=X.Y.M -Dmaven_version=X.Y.M clean test}}}
+   . {{{ant -Dversion=X.Y.M -Dspecversion=X.Y.M clean test}}}
   1. Regenerate the "site" docs per [[Website_Update_HOWTO]] so the documentation included
with this release will reflect the correct version number (at the moment, this is specific
to the tutorial)
   1. Commit the build.xml and documentation changes from the previous few steps.
-  1. Produce one or more release candidates using the steps outlined here, up to the point
of actually tagging the release and distributing it.  Ask on solr-dev (cc general@lucene.apache.org
) for reviewers of the release candidates.  When a consensus emerges, build the final release
candidate and call a vote.  3 +1 Lucene PMC votes are technically needed for a release, although
Solr considers all votes equally. (see [[http://www.apache.org/foundation/voting.html#ReleaseVotes|voting]]).
+  1. Produce one or more release candidates using the steps outlined here, up to the point
of actually tagging the release and distributing it.  Ask on dev@ (cc general@lucene.apache.org
) for reviewers of the release candidates.  When a consensus emerges, build the final release
candidate and call a vote.  3 +1 Lucene PMC votes are technically needed for a release, although
Solr considers all votes equally. (see [[http://www.apache.org/foundation/voting.html#ReleaseVotes|voting]]).
-   * {{{ant -Dversion=X.Y.M -Dspecversion=X.Y.M -Dmaven_version=X.Y.M prepare-release}}}
- note that if your OS username is not the same as your Apache username, you may need to add
a --username param to the svn call in build.xml target build-site eg <arg value="--username"/>
<arg value="markrmiller"/>
+   * {{{ant -Dversion=X.Y.M -Dspecversion=X.Y.M prepare-release}}} - note that if your OS
username is not the same as your Apache username, you may need to add a --username param to
the svn call in build.xml target build-site eg <arg value="--username"/> <arg value="markrmiller"/>
    * Check that release tgz/zip files looks ok - e.g. uncompress them, run example, work
through the steps of the tutorial, ensure that the javadocs are readable, etc...
-   * Upload dist/solr.tar to your public staging space on people.a.o.and send an email to
solr-dev@ calling the vote.
+   * Upload dist/solr.tar to your public staging space on people.a.o.and send an email to
dev@ calling the vote.
  
   1. Tag the release:
   {{{
@@ -76, +74 @@

    1. {{{scp -p dist/apache-solr-X.Y.M.zip* people.apache.org:/www/www.apache.org/dist/lucene/solr/X.Y}}}
   1. Copy the Maven artifacts to the distribution directory (follow the existing directory
structure), to have them pushed to the central Maven repositories:
   {{{
- cp -R PATH_TO_ARTIFACTS/maven/org/apache/solr /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/
+ cp -R package/maven/org/apache/solr /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/
  }}}
   1. Ensure that the most current keys file is on the distribution site:
    . {{{scp -p KEYS people.apache.org:/www/www.apache.org/dist/lucene/solr/}}}
@@ -88, +86 @@

   1. Deploy new main Lucene site. (You will need to be a PMC member to do this: http://wiki.apache.org/lucene-java/TopLevelProject#Updating_the_Website)
   1. Update Javadoc in {{{people.apache.org:/www/lucene.apache.org/solr/docs/api}}}.
    . NOTE: skip this for now, as this javadoc is currently updated automatically from the
nightly build
-  1. Send announcements to the announce@apache.org, solr-user@, solr-dev@, and general@ lucene
mailing lists.  See the Sample Announcement below.
+  1. Send announcements to the announce@apache.org, solr-user@, dev@, and general@ lucene
mailing lists.  See the Sample Announcement below.
  
  == Post Release ==
   * Housekeeping
    * Mark the version as "released" in Jira (noting the release date)
    * Create the next version in Jira (if it doesn't already exist)
    * Go to JIRA and find all issues that were fixed in the release you just made, whose Status
is Resolved, and do a bulk change to close all of these issues. Uncheck the box that says
"send an email for these changes".
-   * Let solr-dev@ know the trunk is now open for commits
+   * Let dev@ know the trunk is now open for commits
   * Publicity
    * update freshmeat (Yonik owns the project on Freshmeat, he may need to do this one)
    * !TheServerSide blurb (http://www.theserverside.com/news/post.tss)

Mime
View raw message