<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Thanks Stan, <div><br></div><div>This release is few more months. How soon? Are you planning to support 0.2 in the meantime?</div><div><br></div><div>We are really pressed on this transition to 1.0. <div>For instance. Number 1 user error while dealing with YAQL is using == instead of =. </div><div><div>We had this discussion and you and Alex and you suggested it’s easy to redefine. </div><div><br></div><div>But… … The short is we need to move to 1.0 to do it. Because from what I figured so far, in 0.2 I can’t naively extend the an operator, as it won’t parse. I did make it work on 0.2 but this required a hack in the YAQL library itself, need to add ‘==‘ to both lexer.py and parser.py. At least what I figured. </div><div><br></div><div>I see the tokens are already generalized in 1.0. It doesn’t seem to worth backporting it to 0.2, but if this is a way, let us know.</div><div><br></div><div>Mistral is betting on YAQL, please help.</div><div><br></div><div>DZ. </div><div><br></div><div>On Jun 26, 2015, at 2:20 AM, Stan Lagun <<a href="mailto:slagun@mirantis.com">slagun@mirantis.com</a>> wrote:</div><div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">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<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><span style="border-collapse: separate; font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; font-size: inherit;"><span style="font-family:arial;font-size:small">Sincerely yours,<br>Stan Lagun<br>Principal Software Engineer @ Mirantis</span></span><br><span style="border-collapse: separate; font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; font-size: inherit;"><span style="font-family:arial;font-size:small"><br><a href="mailto:slagun@mirantis.com" target="_blank"></a></span></span></div></div></div>
<br><div class="gmail_quote">On Fri, Jun 26, 2015 at 8:17 AM, Renat Akhmerov <span dir="ltr"><<a href="mailto:rakhmerov@mirantis.com" target="_blank">rakhmerov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yes, it’s a pretty important thing that we’d like to clarify as soon as possible.<br>
<br>
Any input from Murano team?<br>
<span class="HOEnZb"><font color="#888888"><br>
Renat Akhmerov<br>
@ Mirantis Inc.<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
> On 26 Jun 2015, at 06:01, Dmitri Zimine <<a href="mailto:dzimine@stackstorm.com">dzimine@stackstorm.com</a>> wrote:<br>
><br>
> Folks,<br>
><br>
> it’s been some time,what’s the news:<br>
><br>
> * Is Murano moving YAQL 1.0 in this cycle?<br>
> * What’s your recommendation for this cycle - stay on 0.2.6 or move on?<br>
> * Any progress on documentation?<br>
><br>
> Thanks, DZ><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>
__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></blockquote></div><br></div></div></body></html>