On 09/14/2016 08:41 AM, Igor Gnatenko wrote:
> Hi,
>
> I have question, how you handle bugs where fix already available in
> upstream, but you don't want to backport that fix yet. What you do
> with bug in our trash-box (bugzilla.redhat.com)?
>
> Probably you use whiteboard to indicate where it w
On 2016-09-14, 12:41 GMT, Igor Gnatenko wrote:
> Probably you use whiteboard to indicate where it was fixed,
> close bug and write into comment that it will be fixed in next
> upstream release or ...?
Either External Trackers (if the tracker is defined), or "See
Also" with URL of the ticket.
M
On Wed, Sep 14, 2016 at 9:12 AM, Florian Weimer wrote:
> On 09/14/2016 02:41 PM, Igor Gnatenko wrote:
>
>> I have question, how you handle bugs where fix already available in
>> upstream, but you don't want to backport that fix yet. What you do
>> with bug in our trash-box (bugzilla.redhat.com)?
>
On 09/14/2016 02:41 PM, Igor Gnatenko wrote:
I have question, how you handle bugs where fix already available in
upstream, but you don't want to backport that fix yet. What you do
with bug in our trash-box (bugzilla.redhat.com)?
Probably you use whiteboard to indicate where it was fixed, close
On Wed, Sep 14, 2016 at 2:45 PM, Josh Boyer wrote:
> On Wed, Sep 14, 2016 at 8:41 AM, Igor Gnatenko wrote:
>> Hi,
>>
>> I have question, how you handle bugs where fix already available in
>> upstream, but you don't want to backport that fix yet. What you do
>> with bug in our trash-box (bugzilla.
On Wed, Sep 14, 2016 at 8:41 AM, Igor Gnatenko wrote:
> Hi,
>
> I have question, how you handle bugs where fix already available in
> upstream, but you don't want to backport that fix yet. What you do
> with bug in our trash-box (bugzilla.redhat.com)?
Why don't you want to backport it?
> Probabl
Hi,
I have question, how you handle bugs where fix already available in
upstream, but you don't want to backport that fix yet. What you do
with bug in our trash-box (bugzilla.redhat.com)?
Probably you use whiteboard to indicate where it was fixed, close bug
and write into comment that it will be