Project

General

Profile

Submissions » History » Version 25

Toshi MARUYAMA, 2015-09-06 11:22
ruby bin/about

1 10 Jean-Philippe Lang
h1. Submissions on redmine.org
2 1 Jean-Philippe Lang
3 13 Mischa The Evil
{{>toc}}
4
5 23 Toshi MARUYAMA
Submissions should be written in English.
6 14 Jean-Philippe Lang
7 11 Jean-Philippe Lang
h2. Submitting a Bug
8 10 Jean-Philippe Lang
9 1 Jean-Philippe Lang
Before submitting a bug report here, please make sure:
10
11
* that you're using an appropriate Rails version (see [[RedmineInstall]])
12
* that your database is up to date, especially if you've just migrated from a previous version or revision (see [[RedmineUpgrade]])
13
* if your problem is related to svn (or any other scm), that the proper binaries are installed on your Redmine host (see [[RedmineRepositories]])
14
15 14 Jean-Philippe Lang
And have a look at the "bug list":http://www.redmine.org/projects/redmine/issues?query_id=1 and the [[FAQ]] to see if it has not already been reported.
16 2 Jean-Philippe Lang
17 1 Jean-Philippe Lang
When filling a bug report, please give the following information with the description of your problem:
18
19 18 Etienne Massip
* your database manager version (eg. PostgreSQL 8.2)
20
* your Ruby version (eg. Ruby 1.8.7)
21
* your Rails version (eg. Rails 2.3.11)
22 1 Jean-Philippe Lang
* your Redmine version (pick the version number in the _Affected version_ field) and the exact revision (eg. r1142) if you're using repository code
23
* your scm binary version (eg. svn 1.4) if your problem is about scm integration
24 24 Toshi MARUYAMA
* your using plugins (eg. Code Review plugin)
25 1 Jean-Philippe Lang
26 22 Jean-Philippe Lang
The simplest way to get information about your environment is to run the following command from within your Redmine installation:
27 20 Toshi MARUYAMA
28 25 Toshi MARUYAMA
Redmine 3.x:
29
<pre>
30
ruby bin/about
31
</pre> 
32
33
Redmine 2.x:
34 20 Toshi MARUYAMA
<pre>
35 1 Jean-Philippe Lang
ruby script/about
36
</pre> 
37 22 Jean-Philippe Lang
38
Also, when reporting an application error, post the error stack trace that you should find in the log file (eg. @log/production.log@). The message displayed by the application (eg. _...An error occurred on the page you were trying to access..._) is useless here.
39
40
If the error you're reporting occurs when running a rake task (example: @rake db:migrate@), rerun the task with the @--trace@ option (example: @rake db:migrate --trace@) and post the full output.
41 7 Karl Heinz Marbaise
42 11 Jean-Philippe Lang
h2. Submitting a Security Vulnerability
43 1 Jean-Philippe Lang
44 17 Jean-Philippe Lang
If you think that you've found a security vulnerability, please report it by sending an email to: @security(at)redmine.org@. Known vulnerabilities that were fixed in Redmine releases are listed on the [[Security Advisories]].
45 9 Jean-Philippe Lang
46 11 Jean-Philippe Lang
h2. Submitting a Feature Request
47 6 Thomas Lecavelier
48
Before submitting a feature request here, please make sure:
49
50
* fill the _subject_ as a sum up of your description
51 1 Jean-Philippe Lang
* 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
52
* please *DON'T* fill the _target version_ field: let the developers decide when integrate
53
* please *DON'T* assign the feature request to anybody, let the developers deal with it
54 11 Jean-Philippe Lang
55 13 Mischa The Evil
h2. Submitting a Wiki improvement
56
57
When you edit a wiki page to improve its content, make sure that you fill the _comment_ field with a descriptive summary of the changes you've made to the page. This way we'll be better able to "monitor" and "maintain" the quality of the actual wiki content.
58
59 1 Jean-Philippe Lang
h2. Submitting a Patch
60
61 13 Mischa The Evil
* Changes should be submitted as a single patch file. Instructions for creating a patch using svn can be found [[Patch|here]].
62
* You should mention the branch/revision your patch is based on and attach it