On Thu, May 15, 2008 at 9:31 AM, Jerome Lacoste <[EMAIL PROTECTED]> wrote: > FYI, > > * created missing components in Jira and added some descriptions > * renamed some Jira Projects to follow naming mojo plugin conventions > (Maven 2.x .... Plugin) > * affected all MOJO issues without component to right component / project > * prefixed some components with '_' to make them appear at the top of > the component list (Plugin Submission, General, Mojo Parent and Mojo > Site)
Related to that, I've opened http://jira.codehaus.org/browse/MOJO-1122: ---------------------------- Define rules/checklists related to Jira project creation for MOJO plugins 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... ---------------------------- Comments appreciated. J --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
