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 <dzim...@stackstorm.com> 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 of =. > We had this discussion and you and Alex and you suggested it’s easy to > redefine. > > 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. > > 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. > > Mistral is betting on YAQL, please help. > > DZ. > > On Jun 26, 2015, at 2:20 AM, Stan Lagun <sla...@mirantis.com> wrote: > > 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 > > <sla...@mirantis.com> > > On Fri, Jun 26, 2015 at 8:17 AM, Renat Akhmerov <rakhme...@mirantis.com> > wrote: > >> 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 <dzim...@stackstorm.com> wrote: >> > >> > 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 Development Mailing List (not for usage questions) >> > Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Serg Melikyan, Senior Software Engineer at Mirantis, Inc. http://mirantis.com | smelik...@mirantis.com +7 (495) 640-4904, 0261 +7 (903) 156-0836
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev