> If you want my inexperienced opinion, a young project is the perfect
> time to start this.
^--- This ---^
> I understand that something like [2] will cause a test to fail when you
> make a major change to a versioned object. But you *want* that. It helps
> reviewers more easily catch contributors to say "You need to update the
> version, because the hash changed". The sooner you start using versioned
> objects in the way they are designed, the smaller the upfront cost, and
> it will also be a major savings later on if something like [1] pops up.
...and the way it will be the least overhead is if it's part of the
culture of contributors and reviewers. It's infinitely harder to take
the culture shift after everyone is used to not having to think about
upgrades, not to mention the technical recovery Ryan mentioned.
It's not my call for Magnum, but long-term thinking definitely pays off
in this particular area.
--Dan
__________________________________________________________________________
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
