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 =:-> <div class="gmail_quote">On Nov 14, 2014 12:29 AM, "Curtis Hovey-Canonical" <<a href="mailto:curtis@canonical.com">curtis@canonical.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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 <a href="http://launchpad.net/~sinzui" target="_blank">http://launchpad.net/~sinzui</a> -- Juju-dev mailing list <a href="mailto:Juju-dev@lists.ubuntu.com">Juju-dev@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a> </blockquote></div>