Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: _General
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
We should clarify at which point plugins should get their own Jira projects. Maybe something like:
- every released plugin should have a dedicated Jira project
- pre-released plugin can have a dedicated Jira project
- sandboxed plugins should have a component under the MOJO
should we define some rules here ?
- Jira project for Mojo plugins are named "Maven 2.x Xxxx Plugin"
And maybe create a check list so that people don't forget to do things when moving out of the sandbox, releasing them, etc...
Issue Links
- relates to
-
MOJO-1123
Create JIRA projects for released plugins
-
Brett started a partly related thread about house cleaning in Dec 2007.
I have no strong opinion about that topic. My only suggestion is to say "must" instead of "should" and "can". "should" expresses only a recommendation, leaving room for violations. If we really want consistency, I don't see a reason why some plugins should be allowed to make exceptions to the rules. If it's out on central (i.e. release and pre-release), it must have a dedicated JIRA project.
As for the check list: I guess you could simply add some section to the guide about Performing a Release. In the end, it's the responsibility of the community to remind developers of following these rules when performing their releases.