Thorsten Leemhuis wrote:
On 01.06.2007 14:43, Josh Boyer wrote:
On Fri, 2007-06-01 at 14:24 +0200, Hans de Goede wrote:
1) Can it cause regressions for existing users? -> No
It can cause new problems.
+1
2) Will it get installed automatically by the relative few people who have
updates -testing enabled, and thus see any kind of testing (atleast if its
installable)? -> No
You're making an assumption that there are few people that enable
updates-testing.
/me has it enabled on nearly all of his machines and that way prevented
at least once or twice in the past that bad updates hit updates-proper
I have updates-testing set up too, but remember it won't install new
packages, only update existing ones. Is anyone going to install all
*new* packages that hit updates-testing automatically ?
3) Is there any added value in a new package first sitting for a few days in
testing -> No (because of 2)
Yes. The QA team can at least install from there and see if it starts.
+1 -- and from what I've heard it looks to me that the new QA stuff
might make it quite easy to just push some kind of button to say "there
is a problem, please don't push"
My biggest question about the whole QA stuff is: while some packages are
nice desktop applications with menu entries, many (most?) new packages
are going to be somewhat obscure libraries, plugins, perl/py modules,
i.e. things that are difficult to test. For example, if i push a new
version of libgnomeuimm26 to updates-testing, will the QA folks know
that the only way to test that is to actually test gcdmaster, workrave,
referencer and wp_tray ?
--
Fedora-maintainers mailing list
Fedora-maintainers@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers
--
Fedora-maintainers-readonly mailing list
Fedora-maintainers-readonly@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly