On 06/21/2016 09:23 AM, Guenter Milde wrote:
> On 2016-06-20, Richard Heck wrote:
>> Note that this is different from having the *resolution* be fixed: These
>> would still have no resolution and so would still turn up the right way in
>> searches.
> Having a keyword "fixed" and a resolution
On 2016-06-20, Richard Heck wrote:
> I propose that bugs meeting that description (such as #4398) simply be
> marked as having status "Fixed". The "Fixed in Master" status seems
> misleading:
For me, "fixed in master" is a clear description of the status while
"fixed" would be misleading
On 06/20/2016 11:04 PM, Jean-Marc Lasgouttes wrote:
Le 20/06/2016 18:37, Richard Heck a écrit :
I propose that bugs meeting that description (such as #4398) simply be
marked as having status "Fixed". The "Fixed in Master" status seems
misleading: They are not going to get fixed in stable. If
Le 20/06/2016 18:37, Richard Heck a écrit :
I propose that bugs meeting that description (such as #4398) simply be
marked as having status "Fixed". The "Fixed in Master" status seems
misleading: They are not going to get fixed in stable. If we mark them
Fixed, it can mean: We are done with
I propose that bugs meeting that description (such as #4398) simply be
marked as having status "Fixed". The "Fixed in Master" status seems
misleading: They are not going to get fixed in stable. If we mark them
Fixed, it can mean: We are done with them.
Note that this is different from having the