You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by Goden Yao <go...@apache.org> on 2016/09/01 21:07:29 UTC
Re: Make Fix Version/s Column mandatory for HAWQ JIRAs
Just a update from INFRA team, they've implemented this request in such a
way as following:
1. When you create a JIRA issue, *Fix Version/s* is not mandatory, but you
can choose to fill in under "Configuration" (check "Fix Version/s", this
column will show up).
2. When you close a JIRA issue, it will become mandatory before you can
close.
I just tested myself and it's working appropriate.
With that being said, please still try to put the right release version as
you can when filing a JIRA and for sure please verify the fixed version
when you close the JIRA.
INFRA JIRA and discussion I had, you can refer to:
https://issues.apache.org/jira/browse/INFRA-12259
Thanks
-Goden
On Wed, Jul 13, 2016 at 10:15 AM Ting(Goden) Yao <ty...@pivotal.io> wrote:
> I've put a request to INFRA:
> https://issues.apache.org/jira/browse/INFRA-12259
>
> If you think the version you need is not on the current list, please send
> email to dev@ and one of the admins can make a call if we should create
> the version.
>
>
> -Goden
>
> On Tue, Jul 12, 2016 at 10:40 AM Oleksandr Diachenko <
> odiachenko@pivotal.io> wrote:
>
>> +1 for making it mandatory.
>>
>> On Mon, Jul 11, 2016 at 9:26 PM, Goden Yao <go...@apache.org> wrote:
>>
>> > Hi,
>> >
>> > As release manager for HAWQ right now, I feel it's hard to track each
>> JIRA
>> > for specific releases when we file JIRAs without "Fix Version/s" column
>> > filled.
>> >
>> > So I want to propose to make this column mandatory.
>> >
>> > If you don't know if the JIRA you filed will make a specific release, we
>> > can default it to "Backlog".
>> >
>> > Any objections / concerns, please chime in and let me know.
>> >
>> > Thanks
>> > -Goden
>> >
>>
>
Re: Make Fix Version/s Column mandatory for HAWQ JIRAs
Posted by Lei Chang <ch...@gmail.com>.
Nice!
_____________________________From: Goden Yao <go...@apache.org>
Sent: 星期五, 九月 2, 2016 5:07 上午
Subject: Re: Make Fix Version/s Column mandatory for HAWQ JIRAs
To: <de...@hawq.incubator.apache.org>
Just a update from INFRA team, they've implemented this request in such a
way as following:
1. When you create a JIRA issue, *Fix Version/s* is not mandatory, but you
can choose to fill in under "Configuration" (check "Fix Version/s", this
column will show up).
2. When you close a JIRA issue, it will become mandatory before you can
close.
I just tested myself and it's working appropriate.
With that being said, please still try to put the right release version as
you can when filing a JIRA and for sure please verify the fixed version
when you close the JIRA.
INFRA JIRA and discussion I had, you can refer to:
https://issues.apache.org/jira/browse/INFRA-12259
Thanks
-Goden
On Wed, Jul 13, 2016 at 10:15 AM Ting(Goden) Yao <ty...@pivotal.io> wrote:
> I've put a request to INFRA:
> https://issues.apache.org/jira/browse/INFRA-12259
>
> If you think the version you need is not on the current list, please send
> email to dev@ and one of the admins can make a call if we should create
> the version.
>
>
> -Goden
>
> On Tue, Jul 12, 2016 at 10:40 AM Oleksandr Diachenko <
> odiachenko@pivotal.io> wrote:
>
>> +1 for making it mandatory.
>>
>> On Mon, Jul 11, 2016 at 9:26 PM, Goden Yao <go...@apache.org> wrote:
>>
>> > Hi,
>> >
>> > As release manager for HAWQ right now, I feel it's hard to track each
>> JIRA
>> > for specific releases when we file JIRAs without "Fix Version/s" column
>> > filled.
>> >
>> > So I want to propose to make this column mandatory.
>> >
>> > If you don't know if the JIRA you filed will make a specific release, we
>> > can default it to "Backlog".
>> >
>> > Any objections / concerns, please chime in and let me know.
>> >
>> > Thanks
>> > -Goden
>> >
>>
>