Download as
Browse Code »

Commit 73b64aafdb300dc56ec05a839238b1a849bf46fb

Authored by Joenio Costa
Committed by Daniela Feitosa
1 parent 4c3e514f
Exists in master and in 29 other branches add_member_task_reject_details, admin_visible_profile, article-list-template, community_notifications, contact_admin_translation, event_fixes, fix_comments_pagination, fix_rails4_organization_ratings, fix_sign_up_form, follow_step_fix, forum_topic_creation, mirror_block_improvements, multi_env_on_remote_user, new_security, noosfero_spb_ci, organization_ratings_improvements, organization_ratings_link_to_profile_stable-spb-1.3, organization_ratings_translations_fix, profile_api_improvements, ratings_minor_fixes, remote_user_fix, send_email_to_admins, stable-spb-1.3, stable-spb-1.3-fixes, stable-spb-1.4, stable-spb-1.5, suggest_rejected_value, web_steps_improvements, xss_terminate_custom_options

Updating release procedure

Showing 2 changed files with 23 additions and 19 deletions   Show diff stats
HACKING
  Diff comments   View file @73b64aa
... ... @@ -86,3 +86,7 @@ you want to enable it then you need to change some files:
86 86  
87 87 3) Add in config/noosfero.yml at development section:
88 88 exception_recipients: [admin@example.com]
  89 +
  90 +== Releasing and building Debian package
  91 +
  92 +See RELEASING file.
... ...
RELEASING
  Diff comments   View file @73b64aa
... ... @@ -12,28 +12,28 @@ This file documents release-related activities.
12 12  
13 13 == Releasing noosfero
14 14  
  15 +Considering you are on Debian GNU/Linux or Debian-bases system
  16 + # apt-get install devscripts debhelper
  17 +
15 18 To prepare a release of noosfero, you must follow the steps below:
16 19  
17   -* finish all requirements and bugs assigned to the to-be-released version
18   -* make sure all tests pass
19   -* write release notes at the version's wiki topic.
20   -* generate package with <tt>rake package</tt>. Your tarball will be under the pkg/
21   - directory, named as noosfero-${VERSION}.tar.gz
22   -* test that the package contains everything that is needed: explode the tarball
23   - in a temporary directory, copy config/database.yml.sqlite3 to
24   - config/database.yml, and make <tt>rake db:migrate</tt> and <tt>rake test</tt>. If
25   - everything is ok, you are done. If not, maybe some files are not going into
26   - the tarball. See lib/tasks/package.rake, probably you'll need to change it.
27   -* Go to the version's wiki topic and edit it to reflect the new reality.
28   -* Attach the generated package to that topic. Before attaching calculate the md5 of the package (with mu5sum and paste the MD5 hash as comment in the attachment form)
  20 +* Finish all requirements and bugs assigned to the to-be-released version
  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
  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.
  27 +* 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 and
  29 + edit WebPreferences and update DEBIAN_REPOSITORY_TOPICS setting
  30 +* Attach the generated packages to that topic. Before attaching calculate the
  31 + sha1 of the package (with sha1sum and paste the SHA1 hash as comment in the
  32 + attachment form)
29 33 * Download the attached and verify the MD5 hash
30   -* create a git tag for the released version with <tt>git tag</tt>.
31   -* IMMEDIATELY change the version in lib/noosfero.rb to the next version. (e.g.
32   - 0.2.0 -> 0.3.0)
33   -* update an eventual demonstration version that you run.
34   -* write an announcement e-mail to the relevant maimling lists pointing to the release notes, and maybe to the demonstration version.
  34 +* Update an eventual demonstration version that you run.
  35 +* Write an announcement e-mail to the relevant mailing lists pointing to the
  36 + release notes, and maybe to the demonstration version.
35 37  
36 38 If you had any problem during these steps, you can do <tt>rake clobber_package</tt> to
37 39 completely delete the generated packages and start the process again.
38   -
39   -
... ...