Re: Updates and delays in signing packages

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

 



On Sat, Jul 18, 2009 at 12:01 AM, Rahul
Sundaram<sundaram@xxxxxxxxxxxxxxxxx> wrote:
> On 07/18/2009 03:11 AM, drago01 wrote:
>> On Fri, Jul 17, 2009 at 11:19 PM, Rahul
>>> Hi,
>>>
>>> I have a concern with the recent delays in signing packages and how best
>>> to handle that. I maintain Gnote in Fedora. This is very actively
>>> maintained and has frequent releases, even weekly. It is also a rather
>>> young project (original release in Apr 1) and I do get bug reports on
>>> crashes and other issues that are better fixed quickly. I prefer not to
>>> push things directly to stable repository. With the recommended time of
>>> 7 days in updates-testing and the delay in signing the package for that
>>> and signing it for updates repo, the package gets obsoleted by Bodhi
>>> with the next release update.  What would be the best way to handle this?
>>
>> You don't have to push _every_ upstream release as an update.
>
> Was I not clear? In my case, I do often have to. They fix important bugs.

Sure but lets say upstream releases every week and you rebase every
second week, whats wrong with that?
Unless they are really critical bugs (dataloss / security).

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[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