Well, we’ve been ready to switch to YAQL-1.0 for a couple of months. We researched it, figured out how our integration would change etc. It’s pretty easy to do from our side. So let’s wait for the official YAQL-1.0.X release on pypi.
Renat Akhmerov @ Mirantis Inc. > On 07 Apr 2015, at 00:56, Stan Lagun <sla...@mirantis.com> wrote: > > The plan was to integrate YAQL 1.0 into Murano so that we could say it is > battle-proven, remove "beta" from version and release on PyPI. And then > probably release v1.0.1 that is YAQL with documentation :) > > Sincerely yours, > Stan Lagun > Principal Software Engineer @ Mirantis > > <mailto:sla...@mirantis.com> > On Mon, Apr 6, 2015 at 9:44 PM, Dmitri Zimine <dzim...@stackstorm.com > <mailto:dzim...@stackstorm.com>> wrote: > Renat, > > following up on the IRC meeting: I recalled one more item, and registered a > blueprint - https://blueprints.launchpad.net/mistral/+spec/yaql-v1-0 > <https://blueprints.launchpad.net/mistral/+spec/yaql-v1-0>I think it’s good > timing to do it in Kilo if YAQL 1.0 is announced; so I propose it for > Kilo-rc1; > > One question is when YAQL 1.0 is going to move to Pypi? we can get it from > github link for some time but ideally should use pypi. Alex, Stan, what’s the > plan? > > DZ. > > >
__________________________________________________________________________ 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
