From 0e91abb2c4d0db92ac639e821a77f0b0676d6e69 Mon Sep 17 00:00:00 2001 From: Rodrigo Souto Date: Tue, 18 Jun 2013 11:10:36 -0300 Subject: [PATCH] Adjusting RELEASING file to new release script --- RELEASING | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/RELEASING b/RELEASING index 89b1038..e83c379 100644 --- a/RELEASING +++ b/RELEASING @@ -19,11 +19,12 @@ To prepare a release of noosfero, you must follow the steps below: * Finish all requirements and bugs assigned to the to-be-released version * Make sure all tests pass -* Change the version in lib/noosfero.rb and debian/changelog to the - to-be-released version (e.g. 0.2.0, 0.3.1) * Write release notes at the version's wiki topic -* Generate packages with rake noosfero:release. Your tarball and deb - pkg will be under the pkg/ directory. This task will create a git tag too. +* Generate packages with rake noosfero:release[(stable|test)]. This task will: + * Update the version in lib/noosfero.rb and debian/changelog. + * Create the tarbal and the deb pkg under pkg/ directory. + * Create a git tag and push it. + * Upload the pkg to the configured repository (if configured) on ~/.dput.cf. * Test that the tarball and deb package are ok * Go to the version's wiki topic and edit it to reflect the new reality * 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: sha1 of the package (with sha1sum and paste the SHA1 hash as comment in the attachment form) * Download the attached and verify the MD5 hash -* Push the new version tag (with git push --tags) * Update an eventual demonstration version that you run. * Write an announcement e-mail to the relevant mailing lists pointing to the release notes, and maybe to the demonstration version. -- libgit2 0.21.2