Re: Marking fixed JIRAs against releases

[Konstantin Boudnik]

Another issue: JIRA has release 1.5, however to my knowledge the project had
at least 
    1.5.0-b1
    1.5.0.final

Which one JIRA's version is related to?
  Cos

On Thu, Jan 21, 2016 at 05:33AM, Konstantin Boudnik wrote:
> There might be a way to enforce it on the JIRA side, I just have no idea, to
> be honest. The best way is to file INFRA and ask them to help
> 
> Cos
> 
> On Tue, Jan 19, 2016 at 04:12PM, Yakov Zhdanov wrote:
> > Cos, very good catch.
> > 
> > 1. Agree with Dmitry that it would be better to enforce version is set on
> > close/resolution.
> > 2. As far as already closed tickets let's have everyone review tickets
> > closed by himself and put proper fixVersion.
> > 
> > --Yakov
> > 
> > 2016-01-19 9:53 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>:
> > 
> > > Cos, to my knowledge, the release notes are generated by searching for a
> > > fix version, so the tickets you are pointing out will likely be missed.
> > >
> > > Generally speaking all fixed tickets should have a fix version. Let’s make
> > > sure that we follow this rule going forward. (Any way to enforce it?)
> > >
> > > D.
> > >
> > > On Mon, Jan 18, 2016 at 3:50 PM, Konstantin Boudnik <c...@apache.org>
> > > wrote:
> > >
> > > > Guys,
> > > >
> > > > as a fall-out from another conversation I've ran the following search on
> > > > JIRA
> > > >
> > > >     project = ignite and status in (Fixed, Closed) and fixVersion is 
> > > > null
> > > >
> > > > and we have 150 (yes, some of them are dups and won't fixes) 
> > > > closed/fixed
> > > > tickets without explicit fixVersion on them. How do we keep track of 
> > > > what
> > > > is a
> > > > particular release and what's not? How the Release Notes are generated?
> > > >
> > > > Regards,
> > > >   Cos
> > > >
> > >

signature.asc
Description: Digital signature