[Grok-dev] Re: Release naming convention revisited...
sebastian at urbantalk.se
Mon Oct 15 13:45:49 EDT 2007
The first rule of usability is to provide what the user expects --
regardless of how stupid you might argue those expectations are.
The first rule of communication is write so people understand --
regardless of how narrowminded the common people might be.
But on the other hand, maybe this is a reminder that the world is
waiting for an official 1.0 release of Grok, so I guess it is kind of
good thing. :)
15 okt 2007 kl. 17.09 skrev Tres Seaver:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Martijn Faassen wrote:
>> Sebastian Ware wrote:
>>> But it is still confusing with regards to the maturity of the code.
>>> Haven't we overintellectualised this, rather than kept it simple and
>>> intuitive for the casual observer?
>> No, I think we're doing it the right way. major.minor.bugfix is a
>> common pattern in the software release world and I see no reason to
>> deviate from this.
>> I agree though that things like 0.10 are ugly. We'll get to 1.0 soon
>> enough though, so we can dump that ugliness.
> I think any ugliness comes only from expectations expect 'decimal'-
> semantics, which we obviously don't have anyway (who ever heard of a
> decimal number with *two* decimal points? or which have arbitrary
> suffixes tacked on?). Version identifiers are tuple-like, period;
> confusing them with arithmetic quatntities is a correctible error,
> shouldn't be coddled.
> - --
> Tres Seaver +1 540-429-0999 tseaver at palladion.com
> Palladion Software "Excellence by Design" http://palladion.com
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
> Grok-dev mailing list
> Grok-dev at zope.org
More information about the Grok-dev