You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by Ed Espino <es...@apache.org> on 2016/12/22 21:50:10 UTC
DISCUSSION NEEDED: 2.1.0.0-incubating - what to do with unresolved JIRAs
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 <es...@apache.org>*
Re: DISCUSSION NEEDED: 2.1.0.0-incubating - what to do with
unresolved JIRAs
Posted by Paul Guo <pa...@gmail.com>.
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 <xu...@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 <le...@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 <vv...@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 <rh...@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 <le...@apache.org>
> > wrote:
> > > >
> > > > > Sounds a good idea!
> > > > >
> > > > > Cheers
> > > > > Lei
> > > > >
> > > > >
> > > > > On Fri, Dec 23, 2016 at 5:50 AM, Ed Espino <es...@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 <es...@apache.org>*
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: DISCUSSION NEEDED: 2.1.0.0-incubating - what to do with
unresolved JIRAs
Posted by Hong <xu...@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 <le...@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 <vv...@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 <rh...@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 <le...@apache.org>
> wrote:
> > >
> > > > Sounds a good idea!
> > > >
> > > > Cheers
> > > > Lei
> > > >
> > > >
> > > > On Fri, Dec 23, 2016 at 5:50 AM, Ed Espino <es...@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 <es...@apache.org>*
> > > > >
> > > >
> > >
> >
>
Re: DISCUSSION NEEDED: 2.1.0.0-incubating - what to do with
unresolved JIRAs
Posted by Lei Chang <le...@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 <vv...@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 <rh...@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 <le...@apache.org> wrote:
> >
> > > Sounds a good idea!
> > >
> > > Cheers
> > > Lei
> > >
> > >
> > > On Fri, Dec 23, 2016 at 5:50 AM, Ed Espino <es...@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 <es...@apache.org>*
> > > >
> > >
> >
>
Re: DISCUSSION NEEDED: 2.1.0.0-incubating - what to do with
unresolved JIRAs
Posted by Vineet Goel <vv...@apache.org>.
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 <rh...@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 <le...@apache.org> wrote:
>
> > Sounds a good idea!
> >
> > Cheers
> > Lei
> >
> >
> > On Fri, Dec 23, 2016 at 5:50 AM, Ed Espino <es...@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 <es...@apache.org>*
> > >
> >
>
Re: DISCUSSION NEEDED: 2.1.0.0-incubating - what to do with
unresolved JIRAs
Posted by Ruilong Huo <rh...@pivotal.io>.
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 <le...@apache.org> wrote:
> Sounds a good idea!
>
> Cheers
> Lei
>
>
> On Fri, Dec 23, 2016 at 5:50 AM, Ed Espino <es...@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 <es...@apache.org>*
> >
>
Re: DISCUSSION NEEDED: 2.1.0.0-incubating - what to do with
unresolved JIRAs
Posted by Lei Chang <le...@apache.org>.
Sounds a good idea!
Cheers
Lei
On Fri, Dec 23, 2016 at 5:50 AM, Ed Espino <es...@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 <es...@apache.org>*
>