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 "HowToRelease_Suggestions" by Mark Miller
Date Sun, 06 Mar 2011 15:52:36 GMT
Dear Wiki user,

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

The "HowToRelease_Suggestions" page has been changed by Mark Miller.
http://wiki.apache.org/solr/HowToRelease_Suggestions?action=diff&rev1=8&rev2=9

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

- = Release Suggestins =
+ = Release Suggestions =
  
  [[HowToRelease|Back To HowToRelease]]
  
  This is a list of suggested tasks one might perform when preparing for a release.
  
+ == Check Quality of Artifacts ==
+ 
+  1. Run 
+  {{{
-  1. Run ant clean test
+ ant clean test
+ }}}
   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 "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. Make sure the Ant ''sign-artifacts'' target is in sync with all of the artifacts that
are created. All released artifacts should be signed.
-  1. Is your Key in the KEYS file? people.apache.org:/www/www.apache.org/dist/lucene/solr/KEYS
- http://www.apache.org/dev/release-signing.html
-  1. Run RAT (http://incubator.apache.org/rat/) on the source. ant rat-sources. See https://issues.apache.org/jira/browse/SOLR-762.
+  
+  1. Run RAT on the source 
+  {{{
+ ant rat-sources
+ }}}
+  || {i} || http://incubator.apache.org/rat/||
+  ||  || see https://issues.apache.org/jira/browse/SOLR-762||
-  1. 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...
+  1. 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...
-  1. Check if documentation needs an update, update release date in CHANGES.txt and add any
necessary notes on upgrading.
+  1. Check if documentation needs an update, update release date in '''CHANGES.txt''' and
add any necessary notes on upgrading.
-  1. 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...
+  1. 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...
+  
+ 
+ == Misc Housekeeping ==
-  1. Start a new section in CHANGES.txt
+  1. Start a new section in '''CHANGES.txt'''
+  1. Is your Key in the '''KEYS''' file?
+  || {i} || see people.apache.org:/www/www.apache.org/dist/lucene/solr/KEYS and http://www.apache.org/dev/release-signing.html||
+ == JIRA Housekeeping ==
+ 
+  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 '''Fixed''' Jira issues missing a '''Fix Version''' that
should be marked as fixed in this release.
+  1. Mark the version as '''released''' in Jira (noting the release date)
+  1. Create the next version in Jira (if it doesn't already exist)
+  1. 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.
+  || {i} || Uncheck the box that says "send an email for these changes"||
  
  
  
-  1. Housekeeping
-   1. Mark the version as "released" in Jira (noting the release date)
-   1. Create the next version in Jira (if it doesn't already exist)
-   1. 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".
-   1. Let solr-dev@ know the trunk is now open for commits
  
+ == Publicity ==
  
+  * update [[http://freshmeat.net/|FreshMeat]]
+  || {i} || Yonik owns the project on Freshmeat, he may need to do this one||
+  * [[http://www.theserverside.com/news/post.tss|TheServerSide]] blurb
+  * Blog away!
  
- Publicity
- 
- update freshmeat (Yonik owns the project on Freshmeat, he may need to do this one)
- 

Mime
View raw message