I've been out on vacation but as a circle back to normal (working!) life
I've found this thread very interesting.
I share the concerns raised about the level of resource required to back
this. I don't speak for the VMT but I agree with Jeremy that it should be
possible to provide VMT support to
On 2017-05-24 14:22:14 +0200 (+0200), Thierry Carrez wrote:
[...]
> we ship JARs already:
> http://tarballs.openstack.org/ci/monasca-common/
[...]
Worth pointing out, those all have "SNAPSHOT" in their filenames
which by Apache Maven convention indicates they're not official
releases. Also
Doug Hellmann wrote:
> Excerpts from Davanum Srinivas (dims)'s message of 2017-05-23 10:44:30 -0400:
>> For projects based on Go and Containers we need to ship binaries, for
>
> Can you elaborate on the use of the term "need" here. Is that because
> otherwise the projects can't be consumed? Is it
On 23 May 2017 at 08:13, Doug Hellmann wrote:
> Excerpts from Davanum Srinivas (dims)'s message of 2017-05-23 10:44:30 -0400:
>> Team,
>>
>> Background:
>> For projects based on Go and Containers we need to ship binaries, for
>
> Can you elaborate on the use of the term
Excerpts from Davanum Srinivas (dims)'s message of 2017-05-23 10:44:30 -0400:
> Team,
>
> Background:
> For projects based on Go and Containers we need to ship binaries, for
Can you elaborate on the use of the term "need" here. Is that because
otherwise the projects can't be consumed? Is it the
On 23/05/17 10:44 -0400, Davanum Srinivas wrote:
Team,
Background:
For projects based on Go and Containers we need to ship binaries, for
example Kubernetes, etcd both ship binaries and maintain stable
branches as well.
https://github.com/kubernetes/kubernetes/releases
Team,
Background:
For projects based on Go and Containers we need to ship binaries, for
example Kubernetes, etcd both ship binaries and maintain stable
branches as well.
https://github.com/kubernetes/kubernetes/releases
https://github.com/coreos/etcd/releases/
Kubernetes for example ships