hi, I am not sure Magnum need to introduce reno, which will help user/developer to understand what new feature magnum has recently. I see HouMing Wang already registered a blueprint to add reno(I just registered a new one, after that I found it's registered already, great)

I think it's good to have this. Any though

[1]https://blueprints.launchpad.net/magnum/+spec/add-reno-for-release-management



On 2016年02月26日 09:42, Kai Qiang Wu wrote:
Thanks Hongbin for your info.

I really think it is not good way for new feature introduced.
As new feature introduced often break old work. it more often better with add-in feature is plus, old work still funciton.

Or at least, the error should say "swarm bay now requires trust to work, please use trust related access information before deploy a new swarm bay"

--
Best Regards, Eli(Li Yong)Qiao
Intel OTC China

<<attachment: liyong_qiao.vcf>>

__________________________________________________________________________
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

Reply via email to