Blueprint changed by Antonio Rosales: Whiteboard changed: Charm Store Policy - This is a living policy, we will not try to get it perfect, so trying to get it perfect is not useful, we need to be agile and revisit our policies on a regular basis. - Charm Store doesn't freeze - I want stability. I want a single place to collaborate around. backports? charm store submissions? When to "open" the next release series? Where we've been doing: - Default series is LTS with "juju deploy foo" - Where do we want to go with it: - Default series should be LTS with "juju deploy foo" - Search should default to the best possible solution first. what do we mean by: - - open - able to push to this series - - development focus - default series to build against? + - open - able to push to this series + - development focus - default series to build against? dev focus with release (at beta?) but insure lts gets as much focus as we can - one approach - commit to latest dev focus - try to test on previous release - try to test further back two things to do this: - blacklisting for tests - better automated testing also start forward testing as soon as alpha1 is available perhaps charm browser can show test status for each charm... _per release_ security is an aspect of this when considering preventing, allowing, or automating back-ports maybe don't auto-backport... put on the maintainer's shoulders? what about use tags?... auto-backport only tagged appropriately? (kinda like "pockets" security, etc etc) Tags for charms to denote default behavior perhaps the only valid tags we can use are ones that can be automatically tested? we digress... we branched too late for precise release next time... ? - - q the dev focus on beta1 day? - - what to do with backports? + - q the dev focus on beta1 day? + - what to do with backports? hard problem, we don't have solid answers... maybe we just need to make a decision and run with it follow the distro model, but lag by three months adjust on demand Dev focus to stay on LTS (precise) and push promulgated charms forward and test forward WORK ITEMS? + + Please integrate the spec @ https://wiki.ubuntu.com/BlueprintSpec + [a.rosales].
-- Clarifying Charm Store policy around Ubuntu Releases https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charms-release-policy -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
