© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
I'm just surprised that "make passive policy 1 default" isn't a cleanly cherry-pickable thing. That *sounds* like it should be one line of code :)
Unless it first needs to implement support for "passive policy 1", which it may well need to! But I don't know that unless someone tells me :)
Since the churn *is* necessary, then we should organise testing on a wide variety of laptops - both ones which are expected to have bugs fixed by this upload, and ones which aren't expected to be affected by this upload. The CI lab should have a reasonable selection; what sort of automated testing can be done for this?