the changelog is easy to see in jira
ie 
http://jira.codehaus.org/browse/SUREFIRE?report=com.atlassian.jira.plugin.system.project:roadmap-panel

it's not a problem of tracking the changes but to say out loud "hey,
release the plugin!"

On 9/7/07, nicolas de loof <[EMAIL PROTECTED]> wrote:
> > If you have ideas on how we can do this better, we're all ears.
>
>
> I've noticed from the hudson way (but maybe this is the wrong way) that they
> put a release when 2 or 3 bugs have been fixed.
>
> As maven provides SNAPSHOT support this seems not required to release a
> plugin to allow users to get the fix. But this as the side effect that
> project that want to release must have all dependencies and plugins also
> released.. And many user prefer to have a reproductible build.
>
> IMHO, commiters do great work fixing issues and testing patches, but they
> should go a little more deeper with suggesting releases. A simple rule like
> "when more than N issues have been fixes OR there has been no release from X
> latest weeks, prepare a new release after fixing an issue".
>
> Surefire for example has 96 issues in Jira, so I understand this makes huge
> work for commiters. But there is allready 2 issues marked as CLOSED, one
> from april 07, latest from july. I can't think nobody worked on surefire
> during 5 month !
>
> IMHO a 2.4 (maybe 2.3.1 ?) release should be a good way to make many users
> happy : the ones that reported this issue, and the ones that will fall into
> same situation and may duplicate the ticket.
>
> Why not use the project wiki to create a dashboard for fixed issues, so that
> a new release requirement could be more visible ? I didn't found a simple
> way to get Jira report a list of "closed issue since latest release".
>
> Just my 2 cents...
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to