Juju Charm Store Maintenance

Registered by Jorge Castro on 2012-04-30

Rationale:
Users deploying Charms from the Charm store need to be confident the Charm is in good working condition. Thus, as the numbers of Charms grow there is a need to put a process in place to ensure Charms are being properly maintained.

Goal:
Each Charm has a maintainer, and documentation is available to maintainers on responsibilities for keeping their Charm(s) properly running.

Blueprint information

Status:
Complete
Approver:
Antonio Rosales
Priority:
High
Drafter:
Ubuntu Server Team
Direction:
Approved
Assignee:
Mark Mims
Definition:
Approved
Series goal:
Accepted for quantal
Implementation:
Implemented
Milestone target:
milestone icon ubuntu-12.10
Started by
Kate Stewart on 2012-07-10
Completed by
Clint Byrum on 2012-09-25

Related branches

Sprints

Whiteboard

==========================================================================
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

---

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.

(?)

Work Items

Work items:
[clint-fewbar] update charm tools to support maintainer : DONE
[clint-fewbar] assign maintainers to existing charms, everyone who committed to the charm pinged to see who will maintain it. : DONE
[clint-fewbar] Document orphan process. : DONE
[negronjl] Promulgate should run "charm proof": DONE
[jorge] Update documentation to reflect reality (someone else did this): DONE
[jorge] Announce maintainer field requirement on the mailing list (thanks Clint!): DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.