|Version 4 (modified by BiancaSevillano, 13 months ago) (diff)|
Please join the developer's mailing list (phpeclipse-devel@…, see instructions on http://sourceforge.net/projects/phpeclipse).
Create a ticket
First you have to be registered to be able to create a ticket.
Then when you create the ticket, we ask you include some basic information to help us search through Trac efficiently:
- Short summary: be explicit, also try to be concise
- Description: when creating a ticket (not for editing a previously created one) please give details about the bug you noticed, the feature you want to add.
- Priority: default to normal. Use high only when the bug might be critical.
- Component: which part of PHPEclipse does it apply to?
- Assign to: well assign it to the person who should be notified for this patch. This means you at first step. Then assign it to someone else for feedback, and finally to ed_mann, as he's the one who commits patches.
- Milestone: current milestone is 1.2.0 (this will be updated as per current milestone)
- Version: What version are you working on? It should be the current milestone.
- Keywords: entering 2/3 keywords here may help identifying tickets more easily
- Cc: a email if you want to be notified
That's it, preview it, correct if needed, then submit it.
Use the Eclipse Team functionality to create patches and then attach it to your new ticket. Many small patches are better than fewer, larger patches that fix a single bug or contribute a single feature are better than multi-purpose patches. Expect to move on to direct SVN access after sending in a few good patches - we'd like to grow the active dev team.
Right mouse click on a file, folder or project node in the Navigator view and select menu: Team->Create Patch....
For general background information of the eclipse framework, please see this list of articles: http://eclipse.org/articles/index.html.
Naming your patch
It's nice if you can give the patch a name that has the ticket number in it. Example 699_smarty_tpl_fix_1.patch This is not mandatory, but it does help identify the patches you submit.