>>> I would prefer to leave this as a straight 2.2.4 for 2.0
> what's the upgrade story for users going from S10 to S10+1?
PSARC 2004/676 (Apache 2) sets expectations this way:
6. Exported Interfaces
Interface Name Proposed Stability Comments
Apache 2 code base Evolving
Apache 2 module interface Standard Defined by ASF
Installed location Evolving
svc:/application/apache:v2 Stable FMRI
/var/svc/manifest/application/apache-v2.xml Project Private
manifest
One transiition mechanosm would be to compile and deliver a complete
set of 2.2.4 DSO modules and depend on the customer's old httpd.conf
working with the new server. Unfortunately, I'm not sure how to define
"complete"; the Blastwave configuration might be a good starting place.
> In the currently proposed scenario SUNWsvn will break.
This runs counter to the "Release Quality All the time" expectation
for ON.
I'd suggest that this project needs a dependency on a project to update
svn; it should not integrate before such a project. This implies that
either the two projects need to work together or that this project needs
to increase its scope.
-John
