Hi! A few proposals/questions for the background:
1.) I see a lot of 'open' Jiras hanging although they are already fixed. Usually when working with Jira I use the following workflow: * created if I fix the bug, I set the status to * resolved and if I go on and release the plugin/module i set it to * closed Most times I (or the release manager) use bulk change to pick all the jiras which went into the release and transit it to 'closed' This way we can easily see what got shipped and what is still not public. 2.) Jira has a feature to automatically scan SVN (or any other SCM) and parse the commit messages for any Jira links. (e.g. SCM-493). With this information Jira is able to list all commits directly to the issue (example: [1]) We already write the Jira issue numbers into the commit msg, so why didn't we yet enable this feature? Codehaus don't even has to provide FishEye themselfs because atlassian is so kind to do it for Apache projects. Maybe all this has a reason, but I didn't find it quoted on the list, so I'd be happy to hear about it. txs and LieGrue, strub [1] https://issues.apache.org/jira/browse/OWB-130?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-commits-tabpanel --- On Thu, 9/3/09, Olivier Lamy (JIRA) <[email protected]> wrote: > From: Olivier Lamy (JIRA) <[email protected]> > Subject: [jira] Closed: (MCHANGELOG-103) Does not depend on gitexe provider > To: [email protected] > Date: Thursday, September 3, 2009, 10:50 AM > > [ > http://jira.codehaus.org/browse/MCHANGELOG-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Olivier Lamy closed MCHANGELOG-103. > ----------------------------------- > > Assignee: Olivier Lamy > Resolution: Duplicate > > > Does not depend on gitexe provider > > ---------------------------------- > > > > > Key: MCHANGELOG-103 > > > URL: http://jira.codehaus.org/browse/MCHANGELOG-103 > > > Project: Maven 2.x Changelog Plugin > > Issue Type: Bug > > Affects Versions: 2.1 > > Reporter: > Maarten Billemont > > Assignee: > Olivier Lamy > > > > The plugin specifies a whole bunch of providers > manually. This sounds like pretty bad practice; aside > from that, it does not specify the gitexe provider, > effectively making the plugin useless for repositories using > the GIT SCM. > > Perhaps it should depend on > org/apache/maven/scm/maven-scm-providers-standard or > org/apache/maven/scm/maven-scm instead? > > -- > 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, e-mail: [email protected] For additional commands, e-mail: [email protected]
