© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
@Christopher
We are not living in a very small world.
When I receive a document from a customer written in 3.4.4, edit it with 3.5.2 and return it back, to that customer it will look like *I* broke it.
Do you expect me to tell the customer they have an infrastructure problem?
What you call an EoL version, another person will call 'stable'.
Actually the problem here is a not very well thought through migration path from 3.4.4 to 3.5. The promise of the Open Document Format was that this would never be a problem again, since the format is standardized and would not be allowed to change in a direction that causes backwards compatibility problems. However now the standard has not changed, but the interpretation.
Actually M$ with their ever changing format seem to do a better job in migrating documents and users to a newer product while maintaining backwards compatibility with slower adopters.
Would it not be at least the minimum to warn system administrators of large companies that they may run into this problem before rolling out a new version? The release notes might be the appropriate place.
Ferry