Christian Boos wrote:
> But in the end, it's not *that* important. If we can make Trac 
> advocates' life easier by picking a release numbering scheme reflecting 
> more adequately the level of confidence we have in our product (like in, 
> using major version numbers for our major versions...), I'd personally 
> be OK to do it. If for some reasons there are resistances to change, I 
> wouldn't spend much time on this, continuing with 0.13, 0.14, etc. until 
> the day we feel it would make sense to call it 1.0 also works for me ;-)

How about just shifting by one digit? The next release after 0.12 could
be 1.3 instead of 0.13. This would avoid the psychological burden of the
1.0 release, and would be a way of saying: "Oh, we've been stable for
quite some time, actually."

;-)

-- Remy

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to