<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 24 January 2014 14:36, Michael Schwendt <span dir="ltr"><<a href="mailto:mschwendt@gmail.com" target="_blank">mschwendt@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, 24 Jan 2014 12:39:55 -0800, Adam Williamson wrote:<br>
<br>
> > <a href="https://fedoraproject.org/wiki/Critical_path_package#Actions" target="_blank">https://fedoraproject.org/wiki/Critical_path_package#Actions</a><br>
> ><br>
> > | Packages within the critical path are required to perform the<br>
> > | most fundamental actions on a system. Those actions include:<br>
> > |<br>
> > | [...]<br>
> > | get updates<br>
> > | [...]<br>
> ><br>
> ><br>
> > How to understand that?<br>
><br>
> It also says:<br>
><br>
> graphical network install<br>
> post-install booting<br>
> decrypt encrypted filesystems<br>
> graphics<br>
> login<br>
> networking<br>
> get updates<br>
> minimal buildroot<br>
> compose new trees<br>
> compose live<br>
><br>
> Are we to be expected to re-test every single one of those actions with<br>
> every single critical path update? That seems unreasonable. If that were<br>
> the approach, I think Kevin would have an actual apoplexy while waiting<br>
> for his updates to get released. :)<br>
<br>
</div>It would be unreasonable for a single tester, but "the more testers, the<br>
better".<br></blockquote><div><br></div><div><br></div><div>Looking at the number of people who respond to the qa list at times.. I am going to say there are probably 6-10 active testers during non-release times. It comes and it goes, but that is about the number who seem active at least on lists (and it seems to be that way going over archives for the last couple of years.) So any policy would need to take into account of that limitation.</div>
</div><div><br></div>-- <br><div dir="ltr">Stephen J Smoogen.<br><br></div>
</div></div>