Re: Version Numbering

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Most likely windows support will mean major rewrites of the code base,
> for example there is discussion in hackers about switching from process
> model to thread based model.

A 'major rewrite' of the codebase to support Windows is just not going
to happen in 7.4. The major change in 7.4 is going to be replication.
As Robert pointed out, adding schemas *may* have been a reason to
bump up the number, but the changes from 7.3 to 7.4 do not warrant it.
I will also revisit if the communications protocol is changed,
but arguing that the version number should be changed for marketing
reasons is never going to get you anywhere in the Postgres community.

> For many commercial products there are probably two or even three sets
> of version #s maintained for the product, one for the marketing folks,
> one for the technical people (kept secret) and code revisions.

I don't think "secret" version numbers will work well on an open-source
project. :) You'll also need much better arguments than "that's the way
Microsoft does it" to convince people to adopt arbitrary version
numbering.

Version numbering is a red herring. We have much bigger fish to fry,
such as the lousy website, the bad documentation, and the lack of
built-in replication.

Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200212131008

-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html

iD8DBQE9+fhlvJuQZxSWSsgRAjvXAJ9xxXt7mfsHWPSbcQ17nuBgggiVjQCgk4F6
E/SBhx6HwigCWxbnAjhHyPI=
=2DZH
-----END PGP SIGNATURE-----