Commit 9b0d0209a774e5ff0bd4022514f7d07d433f63be

Authored by AntonioTerceiro
1 parent cf457c4d

ActionItem65: documenting the release process



git-svn-id: https://svn.colivre.coop.br/svn/noosfero/trunk@581 3f533792-8f58-4932-b0fe-aaf55b0a4547
Showing 1 changed file with 20 additions and 0 deletions   Show diff stats
doc/README_FOR_APP
... ... @@ -75,3 +75,23 @@ Use Noosfero Tracker application at http://www.colivre.coop.br/Noosfero.
75 75 * If you have a patch, create an appropriate action item
76 76 (bugs/requirement/enhancement) in the Tracker web (see "Reporting bugs"
77 77 above) of type.
  78 +
  79 +== Releasing noosfero
  80 +
  81 +To prepare a release of noosfero, you must follow the steps below:
  82 +
  83 +* finish all requirements and bugs assigned to the to-be-released version
  84 +* make sure all tests pass
  85 +* write release notes at the version's wiki topic.
  86 +* generate package with +rake package+
  87 +* test that the package contains everything that is needed: explode the tarball
  88 + in a temporary directory, copy config/database.yml.sqlite3 to
  89 + config/database.yml, and make +rake db:migrate+ and +rake test+. If
  90 + everything is ok, you are done. If not, maybe some files are not going into
  91 + the tarball. See lib/tasks/package.rake, probably you'll need to change it.
  92 +* Go to the version's wiki topic and edit it to reflect the new reality.
  93 +* Attach the generated package to that topic.
  94 +* create a svn tag for the released version with +rake tag+. See
  95 + lib/tasks/svn.rake in case of any questions.
  96 +* IMMEDIATELY change the version in lib/noosfero.rb to the next version. (e.g.
  97 + 0.2.0 -> 0.3.0)
... ...