Re: Odd release numbers for development versions?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Robert B(dot) Easter" <reaster(at)comptechnews(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Odd release numbers for development versions?
Date: 2000-06-06 16:07:02
Message-ID: 200006061607.MAA27510@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.

No even/odd mess. Every release is stable.

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-06-06 16:07:44 Protection of debugging options
Previous Message Robert B. Easter 2000-06-06 15:34:36 Odd release numbers for development versions?