Download as
Browse Code »

Commit 48d4e50332147fda120c8576013acb60e236428c

Authored by Antonio Terceiro
1 parent cc29a497
Exists in master and in 13 other branches add_member_task_reject_details, admin_visible_profile, community_notifications, fix_sign_up_form, forum_topic_creation, new_security, organization_ratings_improvements, profile_api_improvements, ratings_minor_fixes, send_email_to_admins, stable-spb-1.4, stable-spb-1.5, web_steps_improvements

Update release procedure to match current reality

Showing 1 changed file with 12 additions and 19 deletions   Show diff stats
RELEASING.md
  Diff comments   View file @48d4e50
... ... @@ -3,37 +3,30 @@ Noosfero release tasks
3 3  
4 4 This file documents release-related activities.
5 5  
6   -Working with translations
7   --------------------------
8   -
9   -* Update translation files: `rake updatepo`. Then `git commit` them.
10   -* Send the PO files to the translators.
11   -* Get the PO files back from translators, put in `po/` under the correct language name (e.,g. `po/pt_BR/`) and `git commit`.
12   -* test translations: `rake makemo` and browse the application on the web.
13   -
14 6 Releasing noosfero
15 7 ------------------
16 8  
17   -Considering you are on a Debian GNU/Linux or Debian-based system
  9 +Considering you are on a Debian GNU/Linux or Debian-based system, the following
  10 +packages are required during the release process:
18 11  
19   - # apt-get install devscripts debhelper
  12 +```
  13 +# apt install git devscripts debhelper
  14 +```
20 15  
21 16 To prepare a release of noosfero, you must follow the steps below:
22 17  
23   -* Finish all requirements and bugs assigned to the to-be-released version
  18 +* Disable the automatic pushing of translation updates in weblate.
24 19 * Make sure all tests pass
25   -* Write release notes at the version's wiki topic
26 20 * Generate packages with `rake noosfero:release[(stable|test)]`. This task will:
27 21 * Update the version in lib/noosfero.rb and debian/changelog.
28 22 * Create the tarbal and the deb pkg under pkg/ directory.
29 23 * Create a git tag and push it.
30   - * Upload the pkg to the configured repository (if configured) on ~/.dput.cf.
  24 + * Upload the packages to the configured repository (if configured) on ~/.dput.cf.
31 25 * Test that the tarball and deb package are ok
32   -* Go to the version's wiki topic and edit it to reflect the new reality
33   -* Edit the topic WebPreferences and update DEBIAN_REPOSITORY_TOPICS setting
34   -* Attach the generated packages to that topic. Before attaching calculate the sha1 of the package (with sha1sum and paste the SHA1 hash as comment in the attachment form)
35   -* Download the attached and verify the MD5 hash
36 26 * Update an eventual demonstration version that you run.
37   -* Write an announcement e-mail to the relevant mailing lists pointing to the release notes, and maybe to the demonstration version.
  27 +* Write an announcement e-mail to the relevant mailing lists pointing to the
  28 + release notes, and maybe to the demonstration version.
  29 +* Re-enable the automatic pushing of trasnlatio updates in weblate.
38 30  
39   -If you had any problem during these steps, you can do `rake clobber_package` to completely delete the generated packages and start the process again.
  31 +If you had any problem during these steps, you can do `rake clobber_package` to
  32 +completely delete the generated packages and start the process again.
... ...