+1 for including a detailed migration guide. I got bit by the small change to attributes from 1.4 to 1.5 :)
Roger Whitcomb | Architect, Engineering | [email protected] | Ingres | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 | USA +1 650-587-5596 | fax: +1 650-587-5550 -----Original Message----- From: Greg Brown [mailto:[email protected]] Sent: Thursday, July 15, 2010 11:45 AM To: [email protected] Subject: Backwards compatibility for WTKXSerializer Given the recent changes to the resource bundle naming conventions, I am wondering if trying to preserve backwards compatibility with WTKXSerializer is sort of an empty gesture. Anyone using resources is going to have to rename those files anyways (it didn't look like there would be an easy way to support both .json and .resources extensions in the Resources class). So I'm not sure how much value preserving only support for .wtkx files will offer. My vote would be to include a detailed 1.5 -> 2.0 migration guide in the README or RELEASE-NOTES that explain specifically what has changed and what needs to be updated. Thoughts?
