maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Benedict <pbened...@apache.org>
Subject Re: What to do with issues that are closed after release ?
Date Mon, 03 Nov 2014 16:25:54 GMT
I would opt to mark them Fixed in the version they were fixed. Although the
release notes emailed out are static, the JIRA release notes are dynamic. I
would look at the latter as the official list.


Cheers,
Paul

On Mon, Nov 3, 2014 at 10:16 AM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:

> On 3 November 2014 16:11, Kristian Rosenvold <kristian.rosenvold@gmail.com
> >
> wrote:
>
> > For some projects like assembly, there are a whole bunch of issues
> > that "later" will turn out to be fixed.
> >
> > For instance assembly plugin had 32 fixed issues at release time, but
> > currently has 35 fixed issues in jira.
> >
> > The problem with this is that these issues never make it into any kind
> > of release announcement; should I tag them as fixed in the next
> > release too ?
> >
>
> So you are suggesting adding a (to be released) version to the jira
> issue...
>
> What happens if there is a regression before you release the next version?
>
> I think just let JIRA reflect our best understanding of the state of play.
>
> Let the announcement mails reflect our best understanding of the state of
> play at that time
>
> Unless you are committing a test case towards the next version, I would not
> add it to two versions... (and we need to add it to the true fixed version
> to reflect reality)
>
>
> >
> > (http://jira.codehaus.org/browse/MASSEMBLY-474 is an example; fixed in
> > 2.5 but I just recently verified the testcase)
> >
> > Kristian
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message