Marnie, > http://httpd.apache.org/dev/release.html - for the HTTPD release > process > definition
Sounds like a reasonable process to me. > > ... and the Incubator release info: > > http://incubator.apache.org/guides/releasemanagement.html#best- > practice-prepare-documentation Yikes! Please don't :) If I may offer a humble suggestion here: Could we please first agree on what to release and what may constitute a good reason to plan a release? My point here is that it would be really nice if the entire project was working alongside the same plan. Right now we have the C++ code going in one direction, the Java code going into a somewhat different direction, the .NET code playing catchup, and I don't even know what the python and ruby code bases are. For example, it would seem sensible, while the protocol spec is in flux, to align one way or another the project releases with the protocol releases. That is to say, if we define protocol version Y as being of interest to the project, either target it all, or don't target it at all. Otherwise, getting the interop in place just among our different code bases will be too painful, not to even speak of interoping with other protocol implementations. Any comments? Tomas Restrepo http://www.winterdom.com/weblog/
