You are not logged in.

#1 2016-06-21 09:49:17

mis
Member
Registered: 2016-03-16
Posts: 234

[Solved] How to handle open bugs fixed in git version

I am wondering how to handle an open bug (of an Arch Linux project) that is fixed in git but no version with the fix was released yet.

File a closure request now, or wait until the next version including the fix is released?

Last edited by mis (2017-03-29 12:10:41)

Offline

#2 2016-06-21 10:51:13

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,787
Website

Re: [Solved] How to handle open bugs fixed in git version

I'd leave it up to the assignee to decide when to close the bug. I think there's some merit in leaving bugs open until they're fixed in stable, but assignees often close bugs with a "Fixed in -git, commit #abcdefg", at which point you could possibly backport the commit to the stable version using ABS if you really need to.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#3 2016-06-21 11:00:48

mis
Member
Registered: 2016-03-16
Posts: 234

Re: [Solved] How to handle open bugs fixed in git version

WorMzy wrote:

I'd leave it up to the assignee to decide when to close the bug.

The question came to mind because I found some bugs that were simply forgotten to close after (some month) the version with the fix was released.
They had no assignee ...

edit: at least no 'assigned to' just status assigned

edit: Ok, then I think waiting until the new version is released and only file a closure request if the bug is not closed after a while is the way to go...

Last edited by mis (2016-06-21 11:13:34)

Offline

Board footer

Powered by FluxBB