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 9:12 AM, Florian Weimer <fweimer@xxxxxxxxxx> 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)?
>>
>> 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 ...?
>
>
> I tend to upload the fixed version to rawhide and resolve the bug as
> CLOSED/RAWHIDE.

Also a fine alternative and less error prone in forgetting to actually fix it.

I think all of these solutions simply illustrate that there is no
fixed process for Fedora bugs, so common sense to the situation needs
to be used.

josh
--
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