No, the discussion below is the question; "Should release 0.9.x follow after 0.9.x-dev? Or shouldn't we release 0.9.(x+1) following the efforts in 0.9.x-dev?"
The standing issue is this; libapr.so.0.9.2 points at one set of functions. The -dev flavors may be patched with new functions in-progress, but if you use one of those functions and drop that binary onto a machine with an "OFFICIAL" libapr.so.0.9.2 the app won't start, because the old .2 version didn't include apr_foo_fn which will be in libapr.so.0.9.3 when it's released. I would prefer the release number follows the -dev effort, and so would a few others - but that throws off our current users. The only way to begin this change, I believe, is to wait for 1.0.0 to begin using this schema, if we want to adopt it. The original point of this thread, the patch, will be in 0.9.3, since 0.9.2 is done. Bill At 11:30 AM 3/28/2003, you wrote: >--On Sunday, March 23, 2003 5:39 PM -0600 "William A. Rowe, Jr." <[EMAIL >PROTECTED]> wrote: > >>>Heh, so did you silently drop the 0.9.2-dev => 0.9.2 schema? I thought the >>>next release is going to be 0.9.2? >> >>I believe Greg and others argued vocally against that change. We can >>revisit that decision as we approach 1.0 - but I'd leave it alone for 0.9. >>No consensus was reached either way. > >The issue was that APR_0_9_2 was already tagged. You can't touch it. It's >done. Ship it. > >Once the tag happens, you can't go back or change the tag. Any fixes *after* >the tag *must* be in the next release. -- justin
