Project

General

Profile

Submissions » History » Version 30

Holger Just, 2024-04-02 18:50
Update example softweare versions

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 30 Holger Just
* your database manager version (e.g. PostgreSQL 9.2)
20
* your Ruby version (e.g. Ruby 3.2.2)
21
* your Redmine version (pick the version number in the _Affected version_ field) and the exact revision (eg. r22769) if you're using repository code
22
* your scm binary version (e.g. svn 1.14.3, or git 2.44.0) if your problem is about scm integration
23 24 Toshi MARUYAMA
* your using plugins (eg. Code Review plugin)
24 1 Jean-Philippe Lang
25 22 Jean-Philippe Lang
The simplest way to get information about your environment is to run the following command from within your Redmine installation:
26 20 Toshi MARUYAMA
27 25 Toshi MARUYAMA
<pre>
28
ruby bin/about
29 1 Jean-Philippe Lang
</pre> 
30
31
When reporting an application error, post the full 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.
32
33 27 Holger Just
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.
34 29 Holger Just
35
If you have installed Redmine using an external package manager, such as the @redmine@ package on Debian/Ubuntu, a Bitnami VM, or a pre-built Docker image, please contact the support channels for these package manager instead unless you are very sure that the issue is specifically caused by Redmine itself. These packages are not maintained by the Redmine team. Often, they have custom changes applied or require specific setup steps which we do not known and generally can't help you with.
36 7 Karl Heinz Marbaise
37 11 Jean-Philippe Lang
h2. Submitting a Security Vulnerability
38 1 Jean-Philippe Lang
39 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]].
40 9 Jean-Philippe Lang
41 11 Jean-Philippe Lang
h2. Submitting a Feature Request
42 6 Thomas Lecavelier
43
Before submitting a feature request here, please make sure:
44
45
* fill the _subject_ as a sum up of your description
46 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
47
* please *DON'T* fill the _target version_ field: let the developers decide when integrate
48
* please *DON'T* assign the feature request to anybody, let the developers deal with it
49 11 Jean-Philippe Lang
50 13 Mischa The Evil
h2. Submitting a Wiki improvement
51
52
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.
53
54 1 Jean-Philippe Lang
h2. Submitting a Patch
55
56 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]].
57
* You should mention the branch/revision your patch is based on and attach it