Download as
Browse Code »

Commit 06e04f9a911411eae649a130cdb42a4c5412f07b

Authored by AntonioTerceiro
1 parent 96e8e656
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

ActionItem65: fix to release documentation 



git-svn-id: https://svn.colivre.coop.br/svn/noosfero/trunk@583 3f533792-8f58-4932-b0fe-aaf55b0a4547
Showing 1 changed file with 5 additions and 1 deletions   Show diff stats
doc/README_FOR_APP
  Diff comments   View file @06e04f9
... ... @@ -83,7 +83,8 @@ To prepare a release of noosfero, you must follow the steps below:
83 83 * finish all requirements and bugs assigned to the to-be-released version
84 84 * make sure all tests pass
85 85 * write release notes at the version's wiki topic.
86   -* generate package with +rake package+
  86 +* generate package with +rake package+. Your tarball will be under the pkg/
  87 + directory, named as noosfero-${VERSION}.tar.gz
87 88 * test that the package contains everything that is needed: explode the tarball
88 89 in a temporary directory, copy config/database.yml.sqlite3 to
89 90 config/database.yml, and make +rake db:migrate+ and +rake test+. If
... ... @@ -96,6 +97,9 @@ To prepare a release of noosfero, you must follow the steps below:
96 97 * IMMEDIATELY change the version in lib/noosfero.rb to the next version. (e.g.
97 98 0.2.0 -> 0.3.0)
98 99  
  100 +If you had any problem during these steps, you can do +rake clobber_package+ to
  101 +completely delete the generated packages and start the process again.
  102 +
99 103 == Working with translations
100 104  
101 105 * Update translation files: +rake updatepo+. Then +svn commit+ them.
... ...