| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| 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 17:16:50 |
| Message-ID: | Pine.BSF.4.21.0006061416410.465-100000@thelab.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
not in this life time ...
On Tue, 6 Jun 2000, Robert B. Easter wrote:
> 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
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-06 17:28:45 | Re: Protection of debugging options |
| Previous Message | Karel Zak | 2000-06-06 17:06:00 | Re: day of week |