Sriram Natarajan wrote: > > > Builds are not releases, that's what overcomplicates your example. > > My assumption was that the build number that I had given above as > example will turn out to be actual releases (You know - like a quarterly > developer release that Nevada releases)
Sun's SXDE builds are not production releases, it's just quarterly builds off the development train. There are no hard compatibility/upgrade guarantees[1]. > > At some point the build trains come to an end and there is an actual > > release (S11, Indiana, whatever). When that release comes out it will > > only have one Apache 2.x and one PHP version. > > Hmm.. doesn't that void the multiple release flexibility that some folks > are asking for . The production release doesn't die the day it comes out, it has a [very] long lifetime. What happens when Apache 2.4 comes out? Will it ever be possible to support it on that release (S11/Indiana/whateveritscalled)? [1] In all things moderation of course. If a component version has been integrated a long time already it's quite unlikely we'll bump it to a very incompatible new version right at the end, for example. But it'll be case by case. This was discussed in the context of 2007/168. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
