Can we removed all devel agents from released streams.

[John Meinel]

I don't think we care about older development releases, but if we care at
all, they won't be able to look anywhere but the released stream. (Only
1.21 knows how to handle agent-stream/tools-stream, right?)
I think we have a deeper bug if upgrade juju --version upgrades to anything
that isn't exactly what you asked for.

John
=:->
On Nov 14, 2014 12:29 AM, "Curtis Hovey-Canonical" <curtis at canonical.com>
wrote:

> We have another cases where an env using --upload-tools tried to
> upgrade from 1.18.4 to 1.20.x and got 1.19.x. I want to remove all the
> devel agents from the released streams.
>
> We have already created separate streams for devel and proposed agents
> to ensure environments cannot upgrade to them without explicitly set
> the environment to use them.
>
> I want to ensure we don't have old devel agents in our released
> streams. This will prevent anyone from getting these version from our
> official locations. This may also prevent environments that are idling
> on obsolete version from deploying more units.
>
> Are there other issues that will happen if I remove the devel agents?
> Is this a bad and dangerous idea?
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20141114/e77fb8ea/attachment-0001.html>