Download as
Browse Code »

Commit f22cec835455c1d72c6732b811e6ecadfc24a6da

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

ActionItem85: minor doc fix 



git-svn-id: https://svn.colivre.coop.br/svn/noosfero/trunk@612 3f533792-8f58-4932-b0fe-aaf55b0a4547
Showing 1 changed file with 11 additions and 11 deletions   Show diff stats
doc/README_FOR_APP
  Diff comments   View file @f22cec8
... ... @@ -21,10 +21,10 @@ There are Debian packages available for all of them but ferret. Try:
21 21  
22 22 # aptitude install subversion ruby rake libgettext-ruby libmocha-ruby libsqlite3-ruby rcov
23 23  
24   -Ferret shall enter Debian soon (as +libferret-ruby+). until there you have two options:
  24 +Ferret shall enter Debian soon (as <tt>libferret-ruby</tt>). until there you have two options:
25 25  
26 26 1. build the source package from svn://svn.debian.org/svn/pkg-ruby-extras/packages-wip/libferret-ruby
27   -1. install ferret via rubygems: issue +gem install ferret+ as root (you'll need to install the +rubygems+ package for it)
  27 +1. install ferret via rubygems: issue <tt>gem install ferret</tt> as root (you'll need to install the <tt>rubygems</tt> package for it)
28 28  
29 29 If you have problems with the setup, use the development mailing list. In
30 30 special its possible that the requirements list above is not complete.
... ... @@ -70,8 +70,8 @@ Use Noosfero Tracker application at http://www.colivre.coop.br/Noosfero.
70 70  
71 71 == Helping with development
72 72  
73   -* It's recommended that you subscribe to the "development mailing
74   - list":http://ynternet.net/mailman/listinfo/noosfero
  73 +* It's recommended that you subscribe to the development mailing
  74 + list: http://ynternet.net/mailman/listinfo/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.
... ... @@ -83,27 +83,27 @@ 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+. Your tarball will be under the pkg/
  86 +* generate package with <tt>rake package</tt>. Your tarball will be under the pkg/
87 87 directory, named as noosfero-${VERSION}.tar.gz
88 88 * test that the package contains everything that is needed: explode the tarball
89 89 in a temporary directory, copy config/database.yml.sqlite3 to
90   - config/database.yml, and make +rake db:migrate+ and +rake test+. If
  90 + config/database.yml, and make <tt>rake db:migrate</tt> and <tt>rake test</tt>. If
91 91 everything is ok, you are done. If not, maybe some files are not going into
92 92 the tarball. See lib/tasks/package.rake, probably you'll need to change it.
93 93 * Go to the version's wiki topic and edit it to reflect the new reality.
94 94 * Attach the generated package to that topic.
95   -* create a svn tag for the released version with +rake tag+. See
  95 +* create a svn tag for the released version with <tt>rake tag</tt>. See
96 96 lib/tasks/svn.rake in case of any questions.
97 97 * IMMEDIATELY change the version in lib/noosfero.rb to the next version. (e.g.
98 98 0.2.0 -> 0.3.0)
99 99  
100   -If you had any problem during these steps, you can do +rake clobber_package+ to
  100 +If you had any problem during these steps, you can do <tt>rake clobber_package</tt> to
101 101 completely delete the generated packages and start the process again.
102 102  
103 103 == Working with translations
104 104  
105   -* Update translation files: +rake updatepo+. Then +svn commit+ them.
  105 +* Update translation files: <tt>rake updatepo</tt>. Then <tt>svn commit</tt> them.
106 106 * Send the PO files to the translators.
107 107 * Get tha PO files back from translators, put in po/ under the correct language
108   - name (e.,g. po/pt_BR/) and +svn commit+.
109   -* test translations: +rake makemo+ and browse the application on the web.
  108 + name (e.,g. po/pt_BR/) and <tt>svn commit</tt>.
  109 +* test translations: <tt>rake makemo</tt> and browse the application on the web.
... ...