Project

General

Profile

Submissions » History » Revision 12

Revision 11 (Jean-Philippe Lang, 2009-01-31 14:46) → Revision 12/30 (Jean-Philippe Lang, 2009-01-31 16:01)

h1. Submissions on redmine.org 

 h2. Submitting a Bug 

 Before submitting a bug report here, please make sure: 

 * that you're using an appropriate Rails version (see [[RedmineInstall]]) 
 * that your database is up to date, especially if you've just migrated from a previous version or revision (see [[RedmineUpgrade]]) 
 * if your problem is related to svn (or any other scm), that the proper binaries are installed on your Redmine host (see [[RedmineRepositories]]) 

 And have a look at the "bug list":http://www.redmine.org/projects/redmine/issues?query_id=1 to see if it has not already been reported. 

 When filling a bug report, please give the following information with the description of your problem: 

 * your database version (eg. Postgresql 8.2) 
 * your Ruby version (eg. ruby 1.8.6) 
 * your Rails version (eg. Rails 1.2.6) 
 * your Redmine version (pick the version number in the _Affected version_ field) and the exact revision (eg. r1142) if you're using repository code 
 * your scm binary version (eg. svn 1.4) if your problem is about scm integration 
 * the error stack trace that you should find in the log file if your report is about an error. The message displayed by the app (eg. _...An error occurred on the page you were trying to access. If you continue..._) is useless here. 

 The simplest way to get all the needed information about your Ruby and Ruby on Rails versions is to run: can be acquired by using 

 <pre>ruby script/about</pre> 

 within your Redmine installation. 

 h2. Submitting a Security Vulnerability 

 If you think that you've found a security vulnerability, please report it by sending an email to: @security(at)redmine.org@. 

 h2. Submitting a Feature Request 

 Before submitting a feature request here, please make sure: 

 * fill the _subject_ as a sum up of your description 
 * fill the _description_ as detailed as you can, don't hesitate to describe precisely how this feature should behave, try to add what benefits you're excepting from it 
 * please *DON'T* fill the _target version_ field: let the developers decide when integrate 
 * please *DON'T* assign the feature request to anybody, let the developers deal with it 

 h2. Submitting a Patch 

 * changes should be submitted as a single patch file. Instructions for creating a patch using svn can be found [[Patch|here]]. 
 * you should mention the branch/revision your patch is based on and attach it