nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Nutch Wiki] Update of "Release_HOWTO" by ChrisMattmann
Date Mon, 26 Oct 2015 06:01:12 GMT
Dear Wiki user,

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

The "Release_HOWTO" page has been changed by ChrisMattmann:
https://wiki.apache.org/nutch/Release_HOWTO?action=diff&rev1=42&rev2=43

Comment:
- update release process.

  
  <<TableOfContents(3)>>
  
+ = Prepping the Release Candidate =
- = Preparation =
-         1. Make a branch trunk or 2.x as follows 
-             {{{svn copy https://svn.apache.org/repos/asf/nutch/${path-to-release} }}} 	
	{{{https://svn.apache.org/repos/asf/nutch/branches/branch-X-Y -m "Nutch X.Y branch" }}}
          1. Create a new release in JIRA. If you do not already have these privileges ask
your PMC Chair.
          1. Push off all open issues to the next release; any critical or blocker issues
should be resolved on mailing list. Discuss any issues that you are unsure of on the mailing
list.
- 
- = Prepping the Release Candidate =
          1. From now on, use the branch created above.
  	1. Update version numbers (from X.Y-dev to X.Y) for release in:
  		* nutch-default.xml - http.agent.version property
@@ -20, +16 @@

  	1. Check if documentation needs an update. Although this may be a huge task at any given
time, any minor contribution is better than nothing at all.
  	1. Commit all these changes.
  	1. Make a clean checkout.
- 	1. Build it.
- 		 {{{ant tar}}}
  	1. Run unit tests.
  		 {{{ant test}}}
  	1. Do basic test to see if release looks ok - e.g. install it and run example from tutorial.
@@ -32, +26 @@

          1. Remove the maven-ant-tasks jar from the ivy directory 
          1. If you do svn status, you will see that a pom.xml has been created. Delete this.
It is not required and just confuses users.
  	1. Tag it. 
- 		{{{svn copy https://svn.apache.org/repos/asf/nutch/branches/branch-X-Y }}} 			{{{https://svn.apache.org/repos/asf/nutch/tags/release-X.Y
-m "Nutch X.Y release." }}}	
+ 		{{{svn copy https://svn.apache.org/repos/asf/nutch/trunk }}} 			{{{https://svn.apache.org/repos/asf/nutch/tags/release-X.Y-rcN
-m "Nutch X.Y release." }}}	
- 	1. run the ant targets for '''tar-bin''', '''zip-bin''', '''zip-src''' and '''tar-src'''
(if releasing trunk) and only the latter two if releasing 2.X (this is because 2.x is only
released as source). The generated artifacts can be found in $NUTCH_HOME/dist. 
+ 	1. run the ant targets for '''zip-bin''', '''zip-src''' (if releasing trunk) and only the
latter one if releasing 2.X (this is because 2.x is only released as source). The generated
artifacts can be found in $NUTCH_HOME/dist. 
+         1. Sign it all of the generated artifacts - [[http://www.apache.org/dev/release-signing.html|Step-By-Step
Guide to Signing Releases]] ' - Consider using [[http://github.com/chrismattmann/apachestuff|Chris
Mattmann's Apache Utility Scripts]].
-         1. Sign it all of the generated artifacts - [[http://www.apache.org/dev/release-signing.html|Step-By-Step
Guide to Signing Releases]] '''N.B.''' an md5, sha and asc should accompany each release artifact.
The result (for trunk) should look like this
- {{{
- mary@mary-ISTART-2380 ~/Downloads/apache/branch-1.8/dist $ ls -al
- total 172192
- drwxrwxr-x  2 mary mary     4096 Mar  1 14:24 .
- drwxrwxr-x 10 mary mary     4096 Mar  1 14:16 ..
- -rw-rw-r--  1 mary mary 83696145 Mar  1 14:16 apache-nutch-1.8-bin.tar.gz
- -rw-rw-r--  1 mary mary      836 Mar  1 14:20 apache-nutch-1.8-bin.tar.gz.asc
- -rw-rw-r--  1 mary mary       78 Mar  1 14:21 apache-nutch-1.8-bin.tar.gz.md5
- -rw-rw-r--  1 mary mary      260 Mar  1 14:23 apache-nutch-1.8-bin.tar.gz.sha
- -rw-rw-r--  1 mary mary 85086686 Mar  1 14:17 apache-nutch-1.8-bin.zip
- -rw-rw-r--  1 mary mary      836 Mar  1 14:20 apache-nutch-1.8-bin.zip.asc
- -rw-rw-r--  1 mary mary       75 Mar  1 14:21 apache-nutch-1.8-bin.zip.md5
- -rw-rw-r--  1 mary mary      222 Mar  1 14:23 apache-nutch-1.8-bin.zip.sha
- -rw-rw-r--  1 mary mary  2774577 Mar  1 14:18 apache-nutch-1.8-src.tar.gz
- -rw-rw-r--  1 mary mary      836 Mar  1 14:20 apache-nutch-1.8-src.tar.gz.asc
- -rw-rw-r--  1 mary mary       78 Mar  1 14:22 apache-nutch-1.8-src.tar.gz.md5
- -rw-rw-r--  1 mary mary      260 Mar  1 14:23 apache-nutch-1.8-src.tar.gz.sha
- -rw-rw-r--  1 mary mary  4696103 Mar  1 14:19 apache-nutch-1.8-src.zip
- -rw-rw-r--  1 mary mary      836 Mar  1 14:21 apache-nutch-1.8-src.zip.asc
- -rw-rw-r--  1 mary mary       75 Mar  1 14:22 apache-nutch-1.8-src.zip.md5
- -rw-rw-r--  1 mary mary      222 Mar  1 14:23 apache-nutch-1.8-src.zip.sha
- }}}
-         1. Make sure that '''all artifacts are editable by fellow committers''' e.g. chmod
775
          1. Check out the release management area at https://dist.apache.org/repos/dist/dev/nutch/{release.version}
and copy all artifacts to here then commit this.
-         1. Make sure your pgp key is listed in the Nutch KEYS file located at http://www.apache.org/dist/nutch/KEYS
+         1. Make sure your pgp key is listed in the Nutch KEYS file located at http://www.apache.org/dist/nutch/KEYS
or better yet, use https://id.apache.org/ and add your PGP there, and it will then appear
in [[https://people.apache.org/keys/group/nutch.asc|Apache Nutch's Automatically Generated
Keys]]
          1. Create and open a VOTE thread on user@ and dev@nutch.apache.org. The VOTE must
pass with 3 +1 binding VOTE's before any release can take place. A VOTE thread usually takes
the form
  {{{
- Hi user@ & dev@,
+ Hi Folks,
  
- This thread is a VOTE for releasing Apache Nutch 1.8 RC#2. The release candidate comprises
the following components.
+ A first candidate for the Nutch X.Y release is available at:
  
+   https://dist.apache.org/repos/dist/dev/nutch/X.Y/
- * A staging repository [0] containing various Maven artifacts
- * A branch-1.8 of the trunk code [1]
- * The tagged source upon which we are VOTE'ing [2]
- * Finally, the release artifacts [3] which i would encourage you to verify for signatures
and test.
  
- You should use the following KEYS [4] file to verify the signatures of all release artifacts.
+ The release candidate is a zip archive of the sources in:
+ http://svn.apache.org/repos/asf/nutch/tags/release-X.Y-rcN/
  
- Please VOTE as follows
+ The SHA1 checksum of the archive is
+ <<<fill in>>>
  
+ In addition, a staged maven repository is available here:
- [ ] +1 Push the release, I am happy :)
- [ ] +0 I am not bothered either way
- [ ] -1 I am not happy with this release candidate (please state why)
  
- Firstly thank you to everyone that contributed to Nutch. Secondly, thank you to everyone
that VOTE's. It is appreciated.
+ <<<fill in>>>
  
- Thanks
- Lewis
- (on behalf of Nutch PMC)
+ Please vote on releasing this package as Apache Nutch X.Y.
+ The vote is open for the next 72 hours and passes if a majority of at
+ least three +1 Nutch PMC votes are cast.
  
- p.s. Here's my +1
-  
- [0] https://repository.apache.org/content/repositories/orgapachenutch-1001/
- [1] https://svn.apache.org/repos/asf/nutch/branches/branch-1.8
- [2] https://svn.apache.org/repos/asf/nutch/tags/release-1.8RC%232/
- [3] https://dist.apache.org/repos/dist/dev/nutch/
- [4] https://dist.apache.org/repos/dist/dev/nutch/KEYS
+ [ ] +1 Release this package as Apache Nutch X.Y.
+ [ ] -1 Do not release this package becauseā€¦
+ 
+ Cheers,
+ <<<fill in>>>
+ 
+ P.S. Of course here is my +1.
  }}}
          1. Once the 72 hour period expires it is time to close the VOTE thread with a RESULT
thread. This should simply state the outcome of VOTE'ing (including how many binding VOTE's
were received. Finally it should included whether the VOTE passed and if the released can
be made.
          1. In the instance where the VOTE does not pass, the release manager should roll
bak all of the work above as well as '''DROP''' the staging artifacts.  

Mime
View raw message