On 09/09/2015 12:15 PM, Dougal Matthews wrote:
Hi,
The tripleo-common library appears to be registered or PyPI but hasn't yet had
a release[1]. I am not familiar with the release process - what do we need to
do to make sure it is regularly released with other TripleO packages?
We will also want
On 09/09/2015 12:54 PM, Doug Hellmann wrote:
> Excerpts from Dmitry Tantsur's message of 2015-09-09 12:58:04 +0200:
>> On 09/09/2015 12:15 PM, Dougal Matthews wrote:
>>> Hi,
>>>
>>> The tripleo-common library appears to be registered or PyPI but hasn't yet
>>> had
>>> a release[1]. I am not famili
Excerpts from Dmitry Tantsur's message of 2015-09-09 12:58:04 +0200:
> On 09/09/2015 12:15 PM, Dougal Matthews wrote:
> > Hi,
> >
> > The tripleo-common library appears to be registered or PyPI but hasn't yet
> > had
> > a release[1]. I am not familiar with the release process - what do we need
>
On 09/09/2015 12:15 PM, Dougal Matthews wrote:
Hi,
The tripleo-common library appears to be registered or PyPI but hasn't yet had
a release[1]. I am not familiar with the release process - what do we need to
do to make sure it is regularly released with other TripleO packages?
I think this is
Hi,
The tripleo-common library appears to be registered or PyPI but hasn't yet had
a release[1]. I am not familiar with the release process - what do we need to
do to make sure it is regularly released with other TripleO packages?
We will also want to do something similar with the new python-tr
