| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Neil Conway <neilc(at)samurai(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Stamp releases notes for 8.2.3, 8.1.8, 8.0.12. |
| Date: | 2007-02-07 23:19:54 |
| Message-ID: | 12400.1170890394@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-patches |
Neil Conway <neilc(at)samurai(dot)com> writes:
> If it fixes a real, non-theoretical bug and has been backpatched to a
> stable release branch, I would say in most cases it is worth documenting
> in the release notes. Describing every change made in a new feature
> release (i.e. 8.3.0) would be far too much verbiage, but far fewer
> changes are made to stable branches. Also, documenting all the
> significant changes in stable branch releases is valuable to let users
> identify possible regressions.
Neil has a good point: the documentation policy should be different for
updates to stable branches than it is for a new major release. I think
Bruce's "too small to bother with" policy is about right for major
releases, but if we've bothered to back-patch something then it's
usually worth documenting.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-02-07 23:22:38 | Re: Re: [COMMITTERS] pgsql: Stamp releases notes for 8.2.3, 8.1.8, 8.0.12. |
| Previous Message | Tom Lane | 2007-02-07 23:11:30 | pgsql: Add a function pg_stat_clear_snapshot() that discards any |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-02-07 23:22:38 | Re: Re: [COMMITTERS] pgsql: Stamp releases notes for 8.2.3, 8.1.8, 8.0.12. |
| Previous Message | Neil Conway | 2007-02-07 22:37:44 | Re: Re: [COMMITTERS] pgsql: Stamp releases notes for 8.2.3, 8.1.8, 8.0.12. |