On 09/30/2015 10:08 AM, Dougal Matthews wrote:
Hi,
What is the standard practice for defining public API's for OpenStack
libraries? As I am working on refactoring and updating tripleo-common I have
to grep through the projects I know that use it to make sure I don't break
anything.
Personally
Hi,
What is the standard practice for defining public API's for OpenStack
libraries? As I am working on refactoring and updating tripleo-common I have
to grep through the projects I know that use it to make sure I don't break
anything.
Personally I would choose to have a policy of "If it is
On 09/30/2015 03:15 PM, Ryan Brown wrote:
On 09/30/2015 04:08 AM, Dougal Matthews wrote:
Hi,
What is the standard practice for defining public API's for OpenStack
libraries? As I am working on refactoring and updating tripleo-common
I have
to grep through the projects I know that use it to
On 09/30/2015 04:08 AM, Dougal Matthews wrote:
Hi,
What is the standard practice for defining public API's for OpenStack
libraries? As I am working on refactoring and updating tripleo-common I have
to grep through the projects I know that use it to make sure I don't break
anything.
The API
On 2015-09-30 01:08, Dougal Matthews wrote:
> Hi,
>
> What is the standard practice for defining public API's for OpenStack
> libraries? As I am working on refactoring and updating tripleo-common I have
> to grep through the projects I know that use it to make sure I don't break
> anything.