On 08/26/2015 11:05 AM, Lucas Alvares Gomes wrote:
On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent <chd...@redhat.com> wrote:
On Wed, 26 Aug 2015, Dmitry Tantsur wrote:
Note that this is an API breaking change, which can potentially break
random users of all projects using wsme. I think we should communicate this
point a bit louder, and I also believe it should have warranted a major
version bump.
Yeah, Lucas and I weren't actually aware of the specific impact of that
change until after it was released; part of the danger of being cores-on-
demand rather than cores-by-desire[1].
I'll speak with him and dhellman later this morning and figure out
the best thing to do.
+1, yeah I kinda agree with the major version bump. But also it's
important to note that Ironic which was affected by that was relying
on be able to POST nonexistent fields to create resources and WSME
would just ignore those on versions <= 0.8.0. That's a legitimate bug
that have been fixed in WSME (and projects shouldn't have relied on
that in the first place).
Note that I'm not talking about our projects, I'm talking about our
users, whose automation might become broken after the switch.
Cheers,
Lucas
__________________________________________________________________________
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
