Blueprint changed by Antonio Rosales: Whiteboard changed: ========================================================================== Everything has been copied to the Blueprint https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charmstore-maintenance -Juan ( negronjl ) ========================================================================== Welcome to Ubuntu Developer Summit! Avoiding charm store bitrot... automated testing - Assign maintainers to charms (metadata.yaml) - Failing tests for period of time. - autofiles bug (puts in the "Big List" to be unpromulgated) Policy would be to not promote charm series until it's all green (i.e., no critical bugs) Simplify writing tests: make it easy for users to run their own tests... merge 'charm test' in charm tools --- - Please integrate the spec @ https://wiki.ubuntu.com/BlueprintSpec [a.rosales]. + + User Stories: + * Aaron is a Charm maintainer and has gotten notification that his Charm is currently failing automated testing. Using the Charm maintainer policy he reviews actions needed by him and gets his Charm back into a valid running state. + + Assumptions: + * CharmTester has the ability to notify maintainers of failures. + * Bug(s) filed against a specific charm also have the correct mechanisms to notify Charm maintainers. + + Test Plans: + *Run CharmTester and evaluate if appropriate notifications were sent to Charm maintainers for failing Charms. + + Release Note: + * Provide pointers to charm maintainer policy, and possibly maintainers.
-- Juju Charm Store Maintenance https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charmstore-maintenance -- 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
