Commit 0e91abb2c4d0db92ac639e821a77f0b0676d6e69

Authored by Rodrigo Souto
1 parent caf26446

Adjusting RELEASING file to new release script

Showing 1 changed file with 5 additions and 5 deletions   Show diff stats
@@ -19,11 +19,12 @@ To prepare a release of noosfero, you must follow the steps below: @@ -19,11 +19,12 @@ To prepare a release of noosfero, you must follow the steps below:
19 19
20 * Finish all requirements and bugs assigned to the to-be-released version 20 * Finish all requirements and bugs assigned to the to-be-released version
21 * Make sure all tests pass 21 * Make sure all tests pass
22 -* Change the version in lib/noosfero.rb and debian/changelog to the  
23 - to-be-released version (e.g. 0.2.0, 0.3.1)  
24 * Write release notes at the version's wiki topic 22 * Write release notes at the version's wiki topic
25 -* Generate packages with <tt>rake noosfero:release</tt>. Your tarball and deb  
26 - pkg will be under the pkg/ directory. This task will create a git tag too. 23 +* Generate packages with <tt>rake noosfero:release[(stable|test)]</tt>. This task will:
  24 + * Update the version in lib/noosfero.rb and debian/changelog.
  25 + * Create the tarbal and the deb pkg under pkg/ directory.
  26 + * Create a git tag and push it.
  27 + * Upload the pkg to the configured repository (if configured) on ~/.dput.cf.
27 * Test that the tarball and deb package are ok 28 * Test that the tarball and deb package are ok
28 * Go to the version's wiki topic and edit it to reflect the new reality 29 * Go to the version's wiki topic and edit it to reflect the new reality
29 * Edit the topic WebPreferences and update DEBIAN_REPOSITORY_TOPICS setting 30 * Edit the topic WebPreferences and update DEBIAN_REPOSITORY_TOPICS setting
@@ -31,7 +32,6 @@ To prepare a release of noosfero, you must follow the steps below: @@ -31,7 +32,6 @@ To prepare a release of noosfero, you must follow the steps below:
31 sha1 of the package (with sha1sum and paste the SHA1 hash as comment in the 32 sha1 of the package (with sha1sum and paste the SHA1 hash as comment in the
32 attachment form) 33 attachment form)
33 * Download the attached and verify the MD5 hash 34 * Download the attached and verify the MD5 hash
34 -* Push the new version tag (with git push --tags)  
35 * Update an eventual demonstration version that you run. 35 * Update an eventual demonstration version that you run.
36 * Write an announcement e-mail to the relevant mailing lists pointing to the 36 * Write an announcement e-mail to the relevant mailing lists pointing to the
37 release notes, and maybe to the demonstration version. 37 release notes, and maybe to the demonstration version.