Re: [openstack-dev] [tripleo] pike m2 has been released

2017-06-13 Thread Ben Nemec
On 06/12/2017 02:10 PM, Emilien Macchi wrote: On Mon, Jun 12, 2017 at 7:20 PM, Ben Nemec wrote: On 06/09/2017 05:39 PM, Emilien Macchi wrote: On Fri, Jun 9, 2017 at 5:01 PM, Ben Nemec wrote: Hmm, I was expecting an instack-undercloud

Re: [openstack-dev] [tripleo] pike m2 has been released

2017-06-12 Thread Emilien Macchi
On Mon, Jun 12, 2017 at 7:20 PM, Ben Nemec wrote: > > > On 06/09/2017 05:39 PM, Emilien Macchi wrote: >> >> On Fri, Jun 9, 2017 at 5:01 PM, Ben Nemec wrote: >>> >>> Hmm, I was expecting an instack-undercloud release as part of m2. Is >>> there >>>

Re: [openstack-dev] [tripleo] pike m2 has been released

2017-06-12 Thread Ben Nemec
On 06/09/2017 05:39 PM, Emilien Macchi wrote: On Fri, Jun 9, 2017 at 5:01 PM, Ben Nemec wrote: Hmm, I was expecting an instack-undercloud release as part of m2. Is there a reason we didn't do that? You just released a new tag:

Re: [openstack-dev] [tripleo] pike m2 has been released

2017-06-09 Thread Emilien Macchi
On Fri, Jun 9, 2017 at 5:01 PM, Ben Nemec wrote: > Hmm, I was expecting an instack-undercloud release as part of m2. Is there > a reason we didn't do that? You just released a new tag: https://review.openstack.org/#/c/471066/ with a new release model, why would we

Re: [openstack-dev] [tripleo] pike m2 has been released

2017-06-09 Thread Ben Nemec
Hmm, I was expecting an instack-undercloud release as part of m2. Is there a reason we didn't do that? On 06/08/2017 03:47 PM, Emilien Macchi wrote: We have a new release of TripleO, pike milestone 2. All bugs targeted on Pike-2 have been moved into Pike-3. I'll take care of moving the

[openstack-dev] [tripleo] pike m2 has been released

2017-06-08 Thread Emilien Macchi
We have a new release of TripleO, pike milestone 2. All bugs targeted on Pike-2 have been moved into Pike-3. I'll take care of moving the blueprints into Pike-3. Some numbers: Blueprints: 3 Unknown, 18 Not started, 14 Started, 3 Slow progress, 11 Good progress, 9 Needs Code Review, 7 Implemented