Folks, it might be time to bring this up again...
We have one essential flaw in our versioning approach, it really
doesn't give us a lot of wiggle room after we commit a new API and
release the first tarball, until version 2.0 rolls out, to fix things.
I'd like to advocate for taking httpd's
On Oct 9, 2007 10:48 AM, William A. Rowe, Jr. [EMAIL PROTECTED] wrote:
[X] retain versioning as-is, e.g. 1.3.0 is our next potential 'GA release'
[ ] adopt n.{odd} unstable versioning, e.g. 1.4.0 will be the 'GA release'
If we have API-incompatible changes, then start the 2.x.x process -
but
