Hi Dennis: Dennis Sosnoski wrote: >> I'm going to try and get 1.5.1 out the door ASAP, and will commit to >> at least >> the transports happening along with that. > > Sounds great, Glen! But Axis2 really requires compatible Rampart and > probably Sandesha releases since these implement functionally which is > crucial to Axis2's intended usage. The lagging releases of these other > projects have been problems with past Axis2 releases, too. Is there > anything we can do to assure that users get a fully-functioning web > services stack based on Axis2 as part of a release? > > Perhaps in the future there should be a single release manager for at > least Axis2, transports, and Rampart, with no official release of Axis2 > until the other essential components are also ready for release?
IMO, this would be a bad idea. The goal of the kind of modularity we have, or at least one of the goals, is to enable the components to version and release at different rates. Unless there were incompatible API changes (which certainly do happen) we should be able to release several Axis2 versions during a single Rampart release cycle, or vice versa. In reality, at least so far, we have needed to rev at least Rampart (Sandesha 1.3 works fine with Axis2 1.4 - not sure about 1.5) for compatibility. I'd like to continue pushing for this kind of "loose" coupling between the various pieces, but I do want us to be sensitive to incompatible changes as well - I think there might be a call here for a slightly richer versioning system, but I don't think we need to make the stack all release in lock-step. Thanks, --Glen
