Re: yum: Critical path update in testing for 4 months?

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

 



On Mon, 2015-12-07 at 02:07 +0100, Michael Schwendt wrote:
> On Sun, 06 Dec 2015 16:02:42 -0800, Adam Williamson wrote:
> 
> > On Sun, 2015-12-06 at 19:52 +0100, Michael Schwendt wrote:
> > > On Sun, 6 Dec 2015 15:50:10 +0100, Reindl Harald wrote:
> > >   
> > > > but what is the reason for maintainers building updates without the 
> > > > intention to push them?  
> > > 
> > > There are maintainers, who dislike a lot of things related to the release
> > > processes. They consider bodhi a pain to use. They would prefer doing
> > > things differently, with less work, and more like fire'n'forget as how
> > > they do it within Rawhide.  
> > 
> > That doesn't really add up.
> 
> What doesn't add up?

We were talking about a yum update that had been sitting around for
four months, with +10 karma. Your theory about why this kind of thing
happens doesn't match the facts of that situation: the update submitter
actually had to take specific action to make it so the update wouldn't
get pushed. If they were just 'fire'n'forget', the update would already
have gone stable weeks ago.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://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