Odd release numbers for development versions?

Is PostgreSQL going to start using odd release numbers for development
versions? This is how the Linux kernel is, and some other projects.

Version.release.revision/build

Like 7.0.x would be the current stable branch. 7.1.x, the current development
branch. The next stable branch would be 7.2.x. Within the current even
release stable branch, maybe only do bug fixes. In the odd dev releases, focus
on new/experiemental. Both branches could have very frequent *.x
revisions/builds. I guess you'd have to apply patches to both branches
sometimes, like when a bug is found in 7.0.x, it is patched and the same patch
applied to the 7.1.x if needed.

This way there would be a clear distinction for users what is likely to be good
for production use and what is still unproven.

--
Robert B. Easter
reaster(at)comptechnews(dot)com