Re: Handling bugs which are fixed in upstream, but not released yet

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 14, 2016 at 2:45 PM, Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote:
> On Wed, Sep 14, 2016 at 8:41 AM, Igor Gnatenko <ignatenko@xxxxxxxxxx> 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?
Sometimes it's too much work to backport if there are merge conflicts.
>
>> 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 ...?
>
> CLOSED->UPSTREAM or CLOSED->NEXTRELEASE both exist, but honestly I
> would probably put the bug in DEFERRED if you plan to fix it but can't
> yet for some reason.  A comment describing the timeline for when the
> fix will hit Fedora is probably sufficient.  The key for any of these
> states is to remember to actually do the fix.
>
> josh
> --
> devel mailing list
> devel@xxxxxxxxxxxxxxxxxxxxxxx
> https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx



-- 
-Igor Gnatenko
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux