Simplify use of formula versioning

Bug #720314 reported by Jim Baker
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
pyjuju
Fix Released
Undecided
William Reade

Bug Description

Manually updating the revision element in metadata.yaml is too error prone, especially in a typical test-edit loop.

Some options that have been discussed:

- Use the timestamp when doing a deploy from a local repository.
- Allow for use of bzr to manage this; this would be similar to our existing support in the agents.

These options presumably can be combined in some way.

Related branches

William Reade (fwereade)
Changed in juju:
status: New → In Progress
assignee: nobody → William Reade (fwereade)
milestone: none → eureka
Revision history for this message
William Reade (fwereade) wrote :

Current plan is to make use of the newly-separated revision data (lp:867877) to, on upgrade, set a local charm's revision to max(local-revision, deployed-revision) + 1; thereby forcing an upgrade even if nothing has changed (mildly wasteful of machine resources) but ensuring nobody suffers repeated null upgrades while developing (hideously wasteful of developer resources).

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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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