My main concern would be the risk of destabilizing 1.6.x by reintroducing
upgrade code to support upgrading from both 1.4.x and 1.5.x. So long as
that risk is mitigated by making the changeset minimal and thorough
review/testing, I see no issue with providing a direct upgrade path from
1.4.x/1.5.x -> 1.6.1. I wouldn't want to make it a precedent, though. It's
hard enough supporting upgrades from one prior version.
Christopher L Tubbs IIhttp://gravatar.com/ctubbsii
On Mon, Jun 16, 2014 at 5:24 PM, Sean Busbey <[EMAIL PROTECTED]> wrote: