[Gluster-Maintainers] Bug state change proposal based on the conversation on bz 1630368

[Atin Mukherjee]

Bit late to this, but I’m in favour of the proposal.

The script change should only consider transitioning the bug status from
POST to CLOSED NEXTRELEASE on master branch only. What’d be also ideal is
to update the fixed in version in which this patch will land.

On Mon, 5 Nov 2018 at 21:39, Yaniv Kaul <ykaul at redhat.com> wrote:

>
>
> On Mon, Nov 5, 2018 at 5:05 PM Sankarshan Mukhopadhyay <
> sankarshan.mukhopadhyay at gmail.com> wrote:
>
>> On Mon, Nov 5, 2018 at 8:14 PM Yaniv Kaul <ykaul at redhat.com> wrote:
>> > On Mon, Nov 5, 2018 at 4:28 PM Niels de Vos <ndevos at redhat.com> wrote:
>> >>
>> >> On Mon, Nov 05, 2018 at 05:31:26PM +0530, Pranith Kumar Karampuri
>> wrote:
>> >> > hi,
>> >> >     When we create a bz on master and clone it to the next
>> release(In my
>> >> > case it was release-5.0), after that release happens can we close
>> the bz on
>> >> > master with CLOSED NEXTRELEASE?
>> >
>> >
>> > Since no one is going to verify it (right now, but I'm hopeful this
>> will change in the future!), no point in keeping it open.
>> > You could keep it open and move it along the process, and then close it
>> properly when you release the next release.
>> > It's kinda pointless if no one's going to do anything with it between
>> MODIFIED to CLOSED.
>> > I mean - assuming you move it to ON_QA - who's going to do the
>> verification?
>> >
>> > In oVirt, QE actually verifies upstream bugs, so there is value. They
>> are also all appear in the release notes, with their status and so on.
>>
>> The Glusto framework is intended to accomplish this end, is it not?
>>
>
> If the developer / QE engineer developed a test case for that BZ - that
> would be amazing!
> Y.
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
-- 
- Atin (atinm)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20181106/7128e27d/attachment.html>