We've been delivering ICU 2.1 and 3.2 for several minor releases now. Clearly way more than a life time of a minor release.
We don't EOF off things that easily unless that is absolutely necessary. In fact, I anticipate that we will have to deliver more in the future. Since, as an example, if a SWI team uses ICU 4.0 and another SWI team wants to use say, ICU 5.0 which has a new feature, then we will definitely want to deliver and maintain the both. Also don't get the Volatile as a message that we want to and will switch ICU 4.0.1 with ICU 5.0 within a life time of minor release or anything like that. Volatile means that when we have ICU 4.0.2, i.e., ICU 4.0.1 patched, say, at S11U2, customers be aware that you *might* see changes in interfaces however unlikely that will be and that is the key message. Ienup Nicolas Williams wrote at 02/24/09 12:18: > I'll let an ARC member decide whether this issue is significant. > > IMO ICU is important, and it's important that there be at least one > version that is guaranteed to be on the system for the life of a minor > release. > > Nico
