[
http://jira.codehaus.org/browse/MOJO-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135083#action_135083
]
Benjamin Bentmann commented on MOJO-1122:
-----------------------------------------
Brett started a partly related thread about [house
cleaning|http://www.nabble.com/-proposal--house-cleaning-td14473692.html] 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|http://mojo.codehaus.org/development/performing-a-release.html]. In the
end, it's the responsibility of the community to remind developers of following
these rules when performing their releases.
> Define rules/checklists related to Jira project creation for MOJO plugins
> -------------------------------------------------------------------------
>
> Key: MOJO-1122
> URL: http://jira.codehaus.org/browse/MOJO-1122
> Project: Mojo
> Issue Type: Improvement
> Components: _General
> Reporter: Jerome Lacoste
>
> 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...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email