revision in charm's metadata.yaml is inconvenient

Bug #867877 reported by William Reade
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Fix Released
Undecided
William Reade

Bug Description

Imminent plans to automatically update charms' revisions are made somewhat tricky by the fact that, to do so, we'd have to load-modify-dump metadata.yaml, thereby losing comments (and potentially altering the file's structure, making real changes harder to keep track of). Therefore, we should keep charms' revisions in files called "revision", containing nothing but the revision.

However, we can't afford to spring another breaking change on everybody, so we still have to allow charms with the revision specified in the old format, while encouraging people to use the new format.

Related branches

William Reade (fwereade)
Changed in juju:
status: New → In Progress
assignee: nobody → William Reade (fwereade)
milestone: none → eureka
William Reade (fwereade)
Changed in juju:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.