With YAQL migration on the way [1]
I suggest we include a conversion script to the blueprint [2] and call BP done
when conversion in place.
DZ>
[1] https://review.openstack.org/#/c/206944/
[2] https://blueprints.launchpad.net/mistral/+spec/yaql-v1-0
On Jun 30, 2015, at 3:43 PM, Thomas Goira
On 06/30/2015 07:09 AM, Dmitri Zimine wrote:
> Thanks Stan,
>
> This release is few more months. How soon? Are you planning to support
> 0.2 in the meantime?
>
> We are really pressed on this transition to 1.0.
> For instance. Number 1 user error while dealing with YAQL is using ==
> instead o
Hi Dmitri,
We share your concerns and migration to the new YAQL is our priority too.
Regarding estimates, I would say month in a worst case.
On Tue, Jun 30, 2015 at 8:09 AM, Dmitri Zimine
wrote:
> Thanks Stan,
>
> This release is few more months. How soon? Are you planning to support
> 0.2 in
Thanks Stan,
This release is few more months. How soon? Are you planning to support 0.2 in
the meantime?
We are really pressed on this transition to 1.0.
For instance. Number 1 user error while dealing with YAQL is using == instead
of =.
We had this discussion and you and Alex and you sugge
The plan is to move to yaql 1.0 this release. Please do not merge yaql 1.0
into Mistral yet. Migration is going to happen really soon
Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis
On Fri, Jun 26, 2015 at 8:17 AM, Renat Akhmerov
wrote:
> Yes, it’s a pretty important thing
Yes, it’s a pretty important thing that we’d like to clarify as soon as
possible.
Any input from Murano team?
Renat Akhmerov
@ Mirantis Inc.
> On 26 Jun 2015, at 06:01, Dmitri Zimine wrote:
>
> Folks,
>
> it’s been some time,what’s the news:
>
> * Is Murano moving YAQL 1.0 in this cycle
Folks,
it’s been some time,what’s the news:
* Is Murano moving YAQL 1.0 in this cycle?
* What’s your recommendation for this cycle - stay on 0.2.6 or move on?
* Any progress on documentation?
Thanks, DZ>
__
OpenStack D
