Re: Educating packagers about always making changes in devel / rawhide first

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

 



On Mon, Feb 10, 2014 at 09:55:26AM -0700, Kevin Fenzi wrote:
> On Mon, 10 Feb 2014 17:42:47 +0100
> Till Maas <opensource@xxxxxxxxx> wrote:

> > Isn't AutoQA already running these kind of checks?
> 
> For f19 and f20 updates, yes... in an advisory manner. 
> 
> But not for rawhide since it has no bodhi update to add the comment to
> or know to check. 

It is not the Rawhide update that needs to be checked but the F19/F20
update, because the problem results from the lack of an Rawhide update,
not because a bad one was issued. However, IMHO it makes more sense to
just hook into AutoQA instead of running the same test twice. Also it
would allow to respond in a timely manner which might better help to
educate maintainers instead of when there are several days between the
bad update creation and the reaction to it.

Regards
Till
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[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