iling List (not for usage questions)
Subject: Re: [openstack-dev] [trove] Upcoming specs and blueprints for
Trove/Mitaka
On 10/12/15 18:44 +, Vyvial, Craig wrote:
>Amrith/Victoria,
>
>Thanks for the heads up about this these blueprints for the Mitaka cycle.
This looks like a lot of wor
5 1:53 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [trove] Upcoming specs and blueprints for
> Trove/Mitaka
>
> On 10/12/15 18:44 +, Vyvial, Craig wrote:
> >Amrith/Victoria,
> >
> >Thanks for the heads up a
Flavio,
So we had a quite a few specs in the last cycle that were rushed to be approved
and then code rushed as well. This was meant to make sure that would not happen
again because it ended up hurting us and had to get many of features through
with exceptions. This is by no means a hard spec f
On 10/12/15 18:44 +, Vyvial, Craig wrote:
Amrith/Victoria,
Thanks for the heads up about this these blueprints for the Mitaka cycle. This
looks like a lot of work but there shouldn’t be a reason to hold back new
blueprints this early in the cycle if they plan on being completed in Mitaka.
Amrith/Victoria,
Thanks for the heads up about this these blueprints for the Mitaka cycle. This
looks like a lot of work but there shouldn’t be a reason to hold back new
blueprints this early in the cycle if they plan on being completed in Mitaka.
Can we get these blueprints written up and subm
2015-12-10 13:10 GMT-03:00 Amrith Kumar :
> Members of the Trove community,
>
> Over the past couple of weeks we have discussed the possibility of an
> early deadline for submission of trove specifications for projects that are
> to be included in the Mitaka release. I understand why we're doing i
Members of the Trove community,
Over the past couple of weeks we have discussed the possibility of an early
deadline for submission of trove specifications for projects that are to be
included in the Mitaka release. I understand why we're doing it, and agree with
the concept. Unfortunately thou
