[Bug 926550] Re: No way to test proposed updates to juju

[Clint Byrum]

** Description changed:

- juju-origin in environments.yaml needs to accept 'distro-proposed', or
- environments.yaml needs to accept some other option that will allow
- directing juju to install the version of juju from the -proposed pocket.
+ [Impact]
+ Users will not be able to test any proposed updates to juju in deployed nodes.
+ 
+ [Dev Fix]
+ Add a new origin "proposed" to that environments will enable the proposed pocket on deployed nodes.
+ 
+ [Stable Fix]
+ Backport of Dev Fix
+ 
+ [Test Case]
+ 1. edit ~/.juju/environments.yaml and set 'origin: proposed' on an environment
+ 2. bootstrap said environment (juju bootstrap -e envname)
+ 3. Verify that bootstrap node has proposed pocket enabled using 'juju ssh 0'. If there are proposed juju updates for that release, verify that juju was installed from proposed.
+ 
+ [Regression Potential]
+ Very Low. The fix just adds a new origin type, 'proposed', so the others are not really affected and the logic leading to all of the origin types is very straightforward. There is also very good test coverage of the affected code.
+ 
+ == Original Bug Description ==
+ 
+ 
+ juju-origin in environments.yaml needs to accept 'distro-proposed', or environments.yaml needs to accept some other option that will allow directing juju to install the version of juju from the -proposed pocket.
  
  The simplest thing is to allow juju-origin to have the URL of a .deb.
  
  This is currently blocking the ability to do an SRU for the bugs fixed
  in juju since the Ubuntu 11.10 release.

** Changed in: juju (Ubuntu Precise)
    Milestone: honolulu => None

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/926550

Title:
  No way to test proposed updates to juju

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/926550/+subscriptions