(Merge/move questions were addressed in this QA meeting: http://meetbot.fedoraproject.org/fedora-meeting/2010-06-28/fedora-qa.2010-06-28-14.59.html) |
m (Fix typo) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Critical Path Actions == | == Critical Path Actions == | ||
I'm not sure where these are. The [[Critical Path Packages]] article provides a very basic list, so I'll refer to that for now. However, our article has some more conditions that are describe in more detail. Should our conditions be merged into the Critical Path Packages article? [[User:Dafrito|Dafrito]] 15:46, 19 June 2010 (UTC) | I'm not sure where these are. The [[Critical Path Packages]] article provides a very basic list, so I'll refer to that for now. However, our article has some more conditions that are describe in more detail. Should our conditions be merged into the Critical Path Packages article? [[User:Dafrito|Dafrito]] 15:46, 19 June 2010 (UTC) | ||
[[User:Bruno|Bruno]]: What is the policy for testing updates with multiple components. Are proven testers expected to install all of the components? The reason I ask this is that a recent kde update had file conflicts (I reported one, but there is a second one affecting just multilib) blocking the update. I gave it a -1, but a proven tester later gave it a +1. I think according to the guidelines, we wouldn't want an update with file conflicts to go out. | |||
Latest revision as of 16:01, 10 July 2010
Critical Path Actions
I'm not sure where these are. The Critical Path Packages article provides a very basic list, so I'll refer to that for now. However, our article has some more conditions that are describe in more detail. Should our conditions be merged into the Critical Path Packages article? Dafrito 15:46, 19 June 2010 (UTC)
Bruno: What is the policy for testing updates with multiple components. Are proven testers expected to install all of the components? The reason I ask this is that a recent kde update had file conflicts (I reported one, but there is a second one affecting just multilib) blocking the update. I gave it a -1, but a proven tester later gave it a +1. I think according to the guidelines, we wouldn't want an update with file conflicts to go out.