hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vineet Goel <vvin...@apache.org>
Subject Re: DISCUSSION NEEDED: 2.1.0.0-incubating - what to do with unresolved JIRAs
Date Fri, 23 Dec 2016 01:02:54 GMT
Agree with Ruilong.

And for JIRA owners, please remember to update the Fix Version when you
close a JIRA. There are many JIRAs which are resolved/closed but Fix
Version = Backlog, which is very confusing for a someone looking to see
which release has the fix.


On Thu, Dec 22, 2016 at 4:52 PM Ruilong Huo <rhuo@pivotal.io> wrote:

> As these issues are not resolved, I think it is more reasonable to mark the
> affected version as 2.1.0.0-incubating and make fix version as backlog.
> Then the correct fix version can be marked at the time when the issue is
> actually resolved.
>
> Best regards,
> Ruilong Huo
>
> On Fri, Dec 23, 2016 at 8:24 AM, Lei Chang <lei_chang@apache.org> wrote:
>
> > Sounds a good idea!
> >
> > Cheers
> > Lei
> >
> >
> > On Fri, Dec 23, 2016 at 5:50 AM, Ed Espino <espino@apache.org> wrote:
> >
> > > We have a significant number of JIRAs opened and currently with a fix
> > > version of 2.1.0.0-incubating. As this is a source only release, I am
> > > inclined to start the branch/tagging release process and update these
> > JIRAs
> > > with the next release version (2.2.0.0-incubating currently available).
> > > Thoughts?
> > >
> > > HAWQ 2.1.0.0-incubating (Open, In Progress, Reopened)
> > > https://issues.apache.org/jira/browse/HAWQ-1232?filter=12339113
> > >
> > > Thanks,
> > > -=e
> > >
> > > FYI: Although we may change the version for the next release, I am
> using
> > > this as a place holder for the next release JIRAs.
> > >
> > > --
> > > *Ed Espino*
> > > *espino@apache.org <espino@apache.org>*
> > >
> >
>

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