Nicolas Williams wrote at 02/24/09 14:47:
> So you won't remove ICU 2.1 and 3.2 from the system?
They are Contracted interfaces. By definition of the interface stability,
unless SWI product teams, i.e., CONSUMERS, no longer need them, there is
no way we can remove them. We can remove them iff CONSUMERS no longer need
them and after following the EOF process.
> OK, that's one part of what I was asking for (multiple versions if
> needed).
As I said, we already have and deliver multiple versions of ICU 2.1 and
3.2 to Solaris. It is clearly also explained in the spec of this case:
This project delivers ICU 4.0.1 as the default libraries, headers, and
utilities as we did for [1]. Existing ICU 2.1 and ICU 3.2 libraries will
still be delivered until the support for each is no longer required by
the contracted SWI product groups. (At that time, we will appropriately
EOF the older versions of libraries as needed.)
> You've shown that some incompatible changes were made at minor releases,
> but what about patch? Do you have any examples of incompatible changes
> made in patch releases? The ICU user guide clearly claims that the ICU
> community intends not to break anything on patch (except for C++).
The example that I gave was on their patch release of ICU 3.8.1 not at
their minor release. (Please read "their" as of ICU's.)
Ienup
