On Wed, Feb 25, 2015 at 09:17:27 -0500, John Ferlan wrote: > On 02/25/2015 07:52 AM, Ján Tomko wrote: ... > > > > ACK both > > If I understand the rules of the road correctly... Since the original > series was reviewed prior to the freeze and this just adjust that, it > seems reasonable to say it's OK for freeze... Actually I'd rather not codify that as a rule. After the freeze everythling should be re-evaluated if it makes sense actually to push. Purpose of the freeze is not to limit new features appearing but have a line where stuff that is likely to break the comming release in any way to be limited. If you get a review for a big feature prior to the freeze and then send a few patches after the freeze it will not make them automagically appear in the RC-package or any less likely to break the release. I think only fixes that target code that was touched in the last devel cycle or fix a obvious bug in a common path should be taken, otherwise we might as well as not have any freeze. Peter
Attachment:
signature.asc
Description: Digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list