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
