upgrade problems Reply-To: OK - So we are being inundated with 2.x to 4.1 upgrade problems.
I see two options: 1) Someone(s) step up to fully test this upgrade path, and resolve issues that are known (plus those that are found while testing). We would wait to release 4.1 until this is all set. 2) We drop support for this upgrade path and require an incremental upgrade to the last 3.x version before you can do 4.1. I want option 1, but it requires someone to step up and drive it to closure. I know that many of the people that might be in the best place to help drive this to closure are off and working on brandy-new features, but isn't (a) upgrade something we consider critical and (b) getting the current feature release target more important? -chip
