Guys, you are awesome. Thank you all very much.
Vladimir Kozhukalov
On Mon, Mar 28, 2016 at 11:50 PM, Alexey Shtokolov
wrote:
> Fuelers!
>
> I'm glad to announce that all patches [0] were merged!
>
> Many thanks to all of you who help us to make Fuel more flexible and
> unlimited.
>
> Special
Fuelers!
I'm glad to announce that all patches [0] were merged!
Many thanks to all of you who help us to make Fuel more flexible and
unlimited.
Special thanks to our code and design reviewers: Igor Kalnitsky, Sergii
Golovatiuk, Vitaly Kramskikh.
And especially to the Team: Bulat Gaifullin, Ilya
Granted. New deadline is 21:00 UTC 03/28/2016.
Vladimir Kozhukalov
On Fri, Mar 25, 2016 at 8:17 PM, Alexey Shtokolov
wrote:
> Fuelers!
>
>
> We are very close to landing our feature "Unlock Settings Tab". But we
> still have a set of reviews [0] to be merged due to several reasons (incl.
> the
Fuelers!
We are very close to landing our feature "Unlock Settings Tab". But we
still have a set of reviews [0] to be merged due to several reasons (incl.
the migration to python27-db gates on OpenStack Infra). I would like to
request extra time till Monday to land them.
[0] - https://goo.gl/kS
Thanks for working this out! Confirming that task history remains
included in the scope of this FFE until the merge deadline, March 24.
On Fri, Mar 11, 2016 at 11:48:51PM +0200, Igor Kalnitsky wrote:
> Hey Dmitry,
>
> I confirm that we agreed on feature design, and you can proceed with
> granting
Hey Dmitry,
I confirm that we agreed on feature design, and you can proceed with
granting exception.
,- Igor
On Fri, Mar 11, 2016 at 8:27 PM, Alexey Shtokolov
wrote:
> Hi Dmitry,
>
> We've reached the design consensus with Igor today. Could you please remove
> the conditional status of the FFE
Hi Dmitry,
We've reached the design consensus with Igor today. Could you please remove
the conditional status of the FFE request?
As agreed: the merge deadline is March 24.
--
WBR, Alexey Shtokolov
2016-03-11 2:27 GMT+03:00 Dmitry Borodaenko :
> Granted. Design consensus deadline for the task h
Granted. Design consensus deadline for the task history part of this
feature is extended to March 11. This does not change the merge deadline
for other parts of this feature, which is still March 24.
--
Dmitry Borodaenko
On Fri, Mar 11, 2016 at 01:02:52AM +0300, Alexey Shtokolov wrote:
> Dmitry
Dmitry,
We are really close to have the consensus, but we need one more meeting
with Fuel-Python Component Lead Igor Kalnitsky to make the final decision.
All patches [0] are on review. The meeting is scheduled for tomorrow (03/11
1:30pm CET).
Could you please grant us one more day for it?
[0] -
Granted, merge deadline March 24, task history part of the feature is to
be excluded from this exception grant unless a consensus is reached by
March 10.
Relevant part of the meeting log starts at:
http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-03-03-16.00.log.html#l-198
--
Dmitry B
Oh, so there is a spec. I was worried that this patch has
"WIP-no-bprint-assigned-yet" string in the commit message, so I thought
there is no spec for it. So the commit message should be updated to avoid
such confusion.
It's really good I've seen this spec. There are plans to overhaul UI data
form
Vitaly
Thanks for bringing this up. Actually the spec has been on review for
almost 2 weeks: https://review.openstack.org/#/c/282695/. Essentially, this
is not introducing new DSL but replacing the existing one with more
powerful extendable language which is being actively developed within
OpenSta
I think it's not a part of best practices to introduce changes like
https://review.openstack.org/#/c/279714/ (adding yet another DSL to the
project) without a blueprint and review and discussion of the spec.
2016-03-02 2:19 GMT+07:00 Alexey Shtokolov :
> Fuelers,
>
> I would like to request a fea
Fuelers,
I would like to request a feature freeze exception for "Unlock settings
tab" feature [0]
This feature being combined with Task-based deployment [1] and
LCM-readiness for Fuel deployment tasks [2] unlocks Basic LCM in Fuel. We
conducted a thorough redesign of this feature and splitted it
14 matches
Mail list logo
