I like Leo's suggestion a few days back to sync everything to the latest framework, it would allow us to re-establish a baseline on the SVN repo. If nobody has a general objection to this, I can (locally) start changing all the projects to depend on framework 4.2-dev and the latest logkit, and see how the tests fare?
Is there any backward incompatibility problems with 4.2, as related to 4.1.5?
If 4.2 is compatible with 4.1.5, I have no issues with that plan. If not, I'd suggest either to release bunch of components compiled against older stable version, and/or ensure that 4.2 is compatible with 4.1.5.
I don't know. On Keel, we too are on 4.1.5. I can try rolling all the components back to 4.1.5 and see if all the tests run (assuming everything compiles), and I agree that would be a good baseline to start. In theory, the second field changing means 4.2.x should be backward-compatible with 4.1.x, I don't know what will happen in practice. We can then turn around and baseline on 4.2 right after that, so we can see the changes between 4.1.5. Of course, somebody might pipe up and tell us before that :-)
Shash
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
