PPAs for juju api client and deployer

[Mark Canonical Ramm-Christensen]

On Wed, Aug 21, 2013 at 3:50 PM, Antonio Rosales <
antonio.rosales at canonical.com> wrote:

> This issue also came up if folks wanted a stable juju, but tools that
> are only housed in devel. The user would have to enable both stable
> and devel PPAs. The issue is when a user updates juju-core they will
> get the devel version, and not the expected stable version.  Thus +1
> on a tools PPA.

I think if a tool is stable and promoted it should definitely go in the
main stable PPA.

I think there is a legitimate use case for devel of core to be separated
out from devel of all the tools -- but in that case it seems unlikely that
a user wants all of the devel tools, they just want one specific one that
solves their problem so that is a use case for tool specific PPA's more
than a general "tools" bucket.

But lest we get tied up in generalities, I'd like to go back to the
specific projects that started this discussion:

*Deployer*

  * We are using promoting and integrating deployer into the GUI
  * Specific versions of juju-core have required specific versions of the
deployer already
  * We use it in cloud deployments

I think that means we have to support it in stable.

*API Client*

  * We aren't yet telling anybody they have to use this and we don't
officially support it

I think this means that it gets to stay in it's own PPA for now, but that
the above arguments would apply and we'd need to get it into devel/stable.

So, from the specific use cases, I see strong value of getting supported
juju extension bits into the stable PPA, and significantly less in getting
them into a unified "devel" PPA.

--Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130821/f4d0c175/attachment.html>