Sriram Natarajan wrote: > > Let us say - for nevada build 74, we are shipping Apache 2.2.4 and the > appropriate PHP 5.2.3 module for apache. Now, let us assume for Nevada > build 90, PHP comes up with a PHP 5.4.2 release . So, at the time of > Nevada build 90 release, we will be bundling Apache 2.2.40 and the also > the appropriate PHP 5.2.18 and PHP 5.4.2 modules for Apache 2.2 Hmm.. > starts getting interested. [...]
Builds are not releases, that's what overcomplicates your example. Right now in ~b74 timeframe it is 2.2.4 and 5.2.3. If newer versions come out in the coming months we'll probably switch to them assuming they work ok and cause no undue disruptions. The old version is gone. 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. (Admittedly there's some uncertainty here with all the Indiana packaging etc, but we'll see.) -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
