Naming your ticket
- You no longer need to prefix your ticket with "[PATCH]", just tag it with patch instead
Tagging
- Please resist from inventing your own tags and choose from the tag cloud.
- Tag tickets with a diff patch or git fork with 'patch'
- If your patch only changes documentation, tag your ticket with 'doc'. Do not tag it with 'patch'.
Authorship (optional)
The name you have set for your Lighthouse profile will be used as the commit author. If you would like to link things nicely with GitHub please leave your email as well. However, if you have a git branch, these details will already be included in the commit. Make sure that the email you provide or create your commit with is the same one you use on GitHub.
Stale Tickets
If a ticket is inactive for a month it may be closed by a Core Team member as stale. If this happens to your ticket and your are still interested in getting it in, please reopen it and provide the suggested changes.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
The latest development for the 1.2.x and 2.0.x releases are on the 1-2-stable and 2-0-stable branches.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
