Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAOPnHqfJ9bgWMMxpmPmfc3woCt8CciGAwhErRV-m=Y-CuTyMRg@mail.gmail.com>
References: <CAHAuQDwVHRyXcNT_7Dh9LGhbdyGSbWR_5QW4+uKY=VRydxnhVg@mail.gmail.com>
 <CAE44UQegDNGh06FMx-7FNLZtngMsOBOJP7FTO=GSCLk5A34B9Q@mail.gmail.com>
 <CAMTypuve8M079HLLrue9c_WvbA4tNV26k7SPF4cAU7ULBgWTmw@mail.gmail.com>
 <CAMLEP5ejhEU3Pr1u22NgqVtOh_Xd=dkMhW1QZ35HpUBe39zOuA@mail.gmail.com>
 <CAE44UQewM2uT3Xqp3trAA2wzCncF=XregGpBEK00mqic2D-k3A@mail.gmail.com> <CAOPnHqfJ9bgWMMxpmPmfc3woCt8CciGAwhErRV-m=Y-CuTyMRg@mail.gmail.com>
From: Paul Guo <paulguo@gmail.com>
Date: Fri, 23 Dec 2016 10:42:13 +0800
Message-ID: <CABQrizfnrCfm8jabkawhSB2=uq=uTQ48D2RJUsoxyF5e-H+p=Q@mail.gmail.com>
Subject: Re: DISCUSSION NEEDED: 2.1.0.0-incubating - what to do with
 unresolved JIRAs
To: dev@hawq.incubator.apache.org
Content-Type: multipart/alternative; boundary=f403045dce04606c2605444a55e9
archived-at: Fri, 23 Dec 2016 02:42:25 -0000

--f403045dce04606c2605444a55e9
Content-Type: text/plain; charset=UTF-8

Just notice this thread. Could JIRA enforce or auto set a specific version?
Ideally we could set a new JIRA as backlog but JIRA auto-change the version
as
the next one when the JIRA is resolved.

2016-12-23 10:18 GMT+08:00 Hong <xunzhang@apache.org>:

> Agree with Lei. "Fixed in a version" would be the next release(
> 2.2.0.0-incubating), the next next release(2.3.0.0-incubating), the next
> big release(3.0.0.0-incubating). It is considered more friendly to HAWQ
> developers and users. Thanks.
>
> 2016-12-23 9:45 GMT+08:00 Lei Chang <lei_chang@apache.org>:
>
> > I think if we are pretty sure that the issue will be fixed in a version,
> it
> > is better to be labeled as the specific version. If we are not sure, it
> is
> > better to label it as "backlog".
> >
> > From external user side, it is much better since they will know when the
> > issues they are watching will be fixed.
> >
> > Cheers
> > Lei
> >
> >
> > On Fri, Dec 23, 2016 at 9:02 AM, Vineet Goel <vvineet@apache.org> wrote:
> >
> > > 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>*
> > > > > >
> > > > >
> > > >
> > >
> >
>

--f403045dce04606c2605444a55e9--