From 73b64aafdb300dc56ec05a839238b1a849bf46fb Mon Sep 17 00:00:00 2001 From: Joenio Costa Date: Fri, 20 May 2011 18:17:51 -0300 Subject: [PATCH] Updating release procedure --- HACKING | 4 ++++ RELEASING | 38 +++++++++++++++++++------------------- 2 files changed, 23 insertions(+), 19 deletions(-) diff --git a/HACKING b/HACKING index e88bc6a..46fef5a 100644 --- a/HACKING +++ b/HACKING @@ -86,3 +86,7 @@ you want to enable it then you need to change some files: 3) Add in config/noosfero.yml at development section: exception_recipients: [admin@example.com] + +== Releasing and building Debian package + +See RELEASING file. diff --git a/RELEASING b/RELEASING index 052de4d..b9cac1c 100644 --- a/RELEASING +++ b/RELEASING @@ -12,28 +12,28 @@ This file documents release-related activities. == Releasing noosfero +Considering you are on Debian GNU/Linux or Debian-bases system + # apt-get install devscripts debhelper + 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 -* write release notes at the version's wiki topic. -* generate package with rake package. Your tarball will be under the pkg/ - directory, named as noosfero-${VERSION}.tar.gz -* test that the package contains everything that is needed: explode the tarball - in a temporary directory, copy config/database.yml.sqlite3 to - config/database.yml, and make rake db:migrate and rake test. If - everything is ok, you are done. If not, maybe some files are not going into - the tarball. See lib/tasks/package.rake, probably you'll need to change it. -* Go to the version's wiki topic and edit it to reflect the new reality. -* 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) +* 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. +* Test that the tarball and deb package are ok +* Go to the version's wiki topic and edit it to reflect the new reality and + edit WebPreferences and update DEBIAN_REPOSITORY_TOPICS setting +* 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) * Download the attached and verify the MD5 hash -* create a git tag for the released version with git tag. -* IMMEDIATELY change the version in lib/noosfero.rb to the next version. (e.g. - 0.2.0 -> 0.3.0) -* update an eventual demonstration version that you run. -* write an announcement e-mail to the relevant maimling lists pointing to the release notes, and maybe to the demonstration version. +* 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. 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. - - -- libgit2 0.21.2