On 2016-12-14 17:49:46 -0600 (-0600), Monty Taylor wrote:
[...]
> For things we generate in pbr - like AUTHORS and ChangeLog - assuming we
> want to do the same thing in go, we could likely come up with something
> similar. I also think we should consider that perhaps those two files
> are not
On 12/14/2016 09:56 AM, Doug Hellmann wrote:
> Excerpts from Dean Troyer's message of 2016-12-14 08:15:08 -0600:
>> On Wed, Dec 14, 2016 at 7:46 AM, Doug Hellmann wrote:
>>> FWIW, some of the deployment tool communities (ansible and puppet,
>>> I think) rely on git repos
On 12/13/2016 04:45 PM, Dean Troyer wrote:
> On Tue, Dec 13, 2016 at 4:26 PM, Jay Pipes wrote:
>> Not sure if it's already been brought up, but I really like govendor:
>
> Govendor and glide are the two most promising candidates at this
> point. I just read today's summary
Excerpts from Dean Troyer's message of 2016-12-14 08:15:08 -0600:
> On Wed, Dec 14, 2016 at 7:46 AM, Doug Hellmann wrote:
> > FWIW, some of the deployment tool communities (ansible and puppet,
> > I think) rely on git repos without external artifacts, and we're
> >
On Wed, Dec 14, 2016 at 7:46 AM, Doug Hellmann wrote:
> FWIW, some of the deployment tool communities (ansible and puppet,
> I think) rely on git repos without external artifacts, and we're
> supporting them in our release tools today. I'm not sure how
> downstream
On Wed, Dec 14, 2016 at 4:25 AM, Thierry Carrez wrote:
> I don't think we need to stop producing and publishing source code
> tarballs in the Go case, just because it's not the primary way people
> consume the code. Publication of the source code is something we need to
>
Excerpts from Dean Troyer's message of 2016-12-13 12:45:07 -0600:
> Release Deliverables
>
> OpenStack still officially considers the tarballs generated during the
> release rpocess to be our official deliverable. Many downstream
> consumers, however, bypass those and go directly to the tagged
>
[Sending again due to mail delivery issues.]
Excerpts from Dean Troyer's message of 2016-12-13 12:45:07 -0600:
> Release Deliverables
>
> OpenStack still officially considers the tarballs generated during the
> release rpocess to be our official deliverable. Many downstream
> consumers,
Monty Taylor wrote:
> On 12/13/2016 12:45 PM, Dean Troyer wrote:
>> Release Deliverables
>>
>> OpenStack still officially considers the tarballs generated during the
>> release rpocess to be our official deliverable. Many downstream
>> consumers, however, bypass those and go directly to the
On Tue, Dec 13, 2016 at 4:26 PM, Jay Pipes wrote:
> Not sure if it's already been brought up, but I really like govendor:
Govendor and glide are the two most promising candidates at this
point. I just read today's summary of the Package Management
Committee [0] and that
On 12/13/2016 03:17 PM, Monty Taylor wrote:
On 12/13/2016 12:45 PM, Dean Troyer wrote:
I am working on scoping the tasks required for the technical pieces of
Golang adoption in OpenStack. This work has been informed somewhat by
flaper87's reference doc proposal[0] for new language additions
On 12/13/2016 12:45 PM, Dean Troyer wrote:
> I am working on scoping the tasks required for the technical pieces of
> Golang adoption in OpenStack. This work has been informed somewhat by
> flaper87's reference doc proposal[0] for new language additions and is
> (mostly) compatible with it,
I am working on scoping the tasks required for the technical pieces of
Golang adoption in OpenStack. This work has been informed somewhat by
flaper87's reference doc proposal[0] for new language additions and is
(mostly) compatible with it, pending that proposal's final approval by
the TC.
As a
13 matches
Mail list logo