On Sep 20, 2005, at 8:18 PM, Daniel John Debrunner wrote:
So is clogging it up with meaningless values for the version numbers. The bigger issue is that we don't really know what that fourth position means. It doesn't seem to mean bugfix release, since it appears we've agreed that's what the third value represents. If we're not ever going to release a version that uses it in a meaningful way, then what is it doing there? At Cloudscape, we bumped the last version whenever a fix was delivered to a customer, which was useful because if you delivered five fixes in a week, all five could have different version numbers with each new version representing the next fix. However, the Apache process for releases - posting a candidate, testing, and then voting - prevents the kind of turnaround on quick fixes that use to make that last position meaningful. Perhaps we should either amend the version policy or figure out a way to make that last number mean something useful. andrew |
- Re: 10.1.2 Release status page Andrew McIntyre
- Re: 10.1.2 Release status page Daniel John Debrunner
- Re: 10.1.2 Release status page TomohitoNakayama
- Re: 10.1.2 Release status page TomohitoNakayama
- Re: 10.1.2 Release status page Kathey Marsden
- Re: 10.1.2 Release status page TomohitoNakayama
- Re: 10.1.2 Release status page Daniel John Debrunner
- Re: 10.1.2 Release status page Ole Solberg
- Re: 10.1.2 Release status page Daniel John Debrunner
- Re: 10.1.2 Release status page Jean T. Anderson
- Re: 10.1.2 Release status page Daniel John Debrunner
