Download as
Browse Code »

Commit 0e91abb2c4d0db92ac639e821a77f0b0676d6e69

Authored by Rodrigo Souto
1 parent caf26446
Exists in master and in 28 other branches 1.2+SPB2, 2_split_by_role, add_fields_in_api, api_fixies, api_pagination, api_private_token, api_tasks, article_hit_count, blog_page_bug, checkbox_to_user_can_edit_page, communities_ratings, communities_ratings_moderation, community_ratings_rebase, fix_cloned_article_parent, fix_gallery_image_url, fix_javascript_categories, fix_optional_fields, fix_suggest_article, fix_user_email_validation, highlight_block_fix, notification_plugin, notification_plugin_rebase, script_to_update, split_by_role, stable, temp_ratings, tests, tests_fixies

Adjusting RELEASING file to new release script

Showing 1 changed file with 5 additions and 5 deletions   Show diff stats
RELEASING
  Diff comments   View file @0e91abb
... ... @@ -19,11 +19,12 @@ To prepare a release of noosfero, you must follow the steps below:
19 19  
20 20 * Finish all requirements and bugs assigned to the to-be-released version
21 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 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 28 * Test that the tarball and deb package are ok
28 29 * Go to the version's wiki topic and edit it to reflect the new reality
29 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 32 sha1 of the package (with sha1sum and paste the SHA1 hash as comment in the
32 33 attachment form)
33 34 * Download the attached and verify the MD5 hash
34   -* Push the new version tag (with git push --tags)
35 35 * Update an eventual demonstration version that you run.
36 36 * Write an announcement e-mail to the relevant mailing lists pointing to the
37 37 release notes, and maybe to the demonstration version.
... ...