Re: standardized backwards incompatibility tag for commits

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: standardized backwards incompatibility tag for commits
Date: 2017-03-25 20:15:39
Message-ID: 31071.1490472939@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Seems like it'd be good to standardize how we're declaring that a commit
> contains backwards incompatible changes. I've seen
> - 'BACKWARDS INCOMPATIBLE CHANGE'
> - 'BACKWARD INCOMPATIBILITY'
> - a lot of free-flow text annotations like "as a
> backward-incompatibility", "This makes a backwards-incompatible change"

> Especially the latter are easy to miss when looking through the commit
> log and I'd bet some get missed when generating the release notes.

Bruce might have a different opinion, but for my own part I do not think
it would make any difference in creating the release notes. The important
thing is that the information be there in the log entry, not exactly how
it's spelled.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-03-25 20:32:33 Re: LWLock optimization for multicore Power machines
Previous Message Alexander Korotkov 2017-03-25 20:11:06 Re: LWLock optimization for multicore Power machines