Re: [openstack-dev] [Mistral] Upgrading to YAQL 1.0
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-0I 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
Re: [openstack-dev] [Mistral] Upgrading to YAQL 1.0
Hi Renat Dmitry Today we released YAQL 1.0.0b2 and release is available on PyPI, I think it's better to start migration to YAQL 1.0.0 right now, we don't expect any major changes, only small bug-fixes that should not affect your integration. And we will release 1.0.0 before end of Kilo cycle. On Tue, Apr 7, 2015 at 11:50 AM, Renat Akhmerov rakhme...@mirantis.com wrote: 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 On Mon, Apr 6, 2015 at 9:44 PM, Dmitri Zimine 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-0I 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 -- Serg Melikyan, Senior Software Engineer at Mirantis, Inc. http://mirantis.com | smelik...@mirantis.com __ 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
Re: [openstack-dev] [Mistral] Upgrading to YAQL 1.0
Ok, sounds good! So if there aren’t any objections we can start doing it asap. Renat Akhmerov @ Mirantis Inc. On 07 Apr 2015, at 16:00, Serg Melikyan smelik...@mirantis.com wrote: Hi Renat Dmitry Today we released YAQL 1.0.0b2 and release is available on PyPI, I think it's better to start migration to YAQL 1.0.0 right now, we don't expect any major changes, only small bug-fixes that should not affect your integration. And we will release 1.0.0 before end of Kilo cycle. On Tue, Apr 7, 2015 at 11:50 AM, Renat Akhmerov rakhme...@mirantis.com wrote: 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 On Mon, Apr 6, 2015 at 9:44 PM, Dmitri Zimine 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-0I 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 -- Serg Melikyan, Senior Software Engineer at Mirantis, Inc. http://mirantis.com | smelik...@mirantis.com __ 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
[openstack-dev] [Mistral] Upgrading to YAQL 1.0
Renat, following up on the IRC meeting: I recalled one more item, and registered a blueprint - https://blueprints.launchpad.net/mistral/+spec/yaql-v1-0I 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
Re: [openstack-dev] [Mistral] Upgrading to YAQL 1.0
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 sla...@mirantis.com On Mon, Apr 6, 2015 at 9:44 PM, Dmitri Zimine 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-0I 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
