On Wed, Jul 9, 2014 at 12:16 PM, roger peppe <rogpe...@gmail.com> wrote: > On 9 July 2014 15:20, Gustavo Niemeyer <gust...@niemeyer.net> wrote: >> Is there a reason to reinvent the API from the ground up, instead of >> extending what exists today? > > We actually started out by thinking that we'd make something > backwardly compatible with the old charm store API, but > we're actually talking about inheriting from two APIs here, > charm-store and charm-world, and after some consideration > we decided to try to make a single API that takes ideas > from both but makes coherent sense in itself.
Are the considerations that justify obsoleting the current charm store API written down anywhere? I'd strongly recommend starting any specification that obsoletes a prior implementation or API by explaining why the current one is unsuitable. This is even more of the case with an API, as people will have to work to fix anything that depends on the previous version, so ideally we avoid that altogether, and in the worst case we at least provide a great justification for why they'll have to do that work. gustavo @ http://niemeyer.net -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
