Comment 13 for bug 1671842

This "1.X" series v "2.0" series is a bit of misnomer and almost exclusively internal changes. I'd be quite confident nobody calling dib from the command line would notice a difference between the two (the only issue we had was with instack, which was using arguably internal python interfaces ... at least, it wasn't well thought out between the two teams). I do not believe anyone pinned themselves to 1.28.0 to avoid 2.0.0. This was all put out there in [1]. ergo, 1.28.0 was mostly a safety release so that if v2 *did* explode for some unknown reason, we could do a v1 branch off it. But this does not appear to have happened, thankfully.

Thus, if somebody has pinned themselves to an old dib release but decides to update, tries >= 2.5.0, reports to us that it doesn't work as a drop-in replacement for them, and it's not something we can trivially fix for them quickly, and 1.28.0 works for them, and they have a specific need for this fix, I would entertain figuring out if activating this branch is the appropriate solution.

[1] http://lists.openstack.org/pipermail/openstack-dev/2017-February/111833.html