Jay Levitt <jay.lev...@gmail.com> writes:
> Greg Smith wrote:
>> Tracking when and how a bug is backported to older versions is one hard part
>> of the problem here.
> That's a great point. Both GitHub and git itself have no real concept of
> releases, and can't tell you when a commit made it in.
We do actually have a somewhat-workable solution for that, see
src/tools/git_changelog. It relies on cooperation of the committers
to commit related patches with the same commit message and more or
less the same commit time, but that fits fairly well with our practices
anyway. If we did have an issue tracker I could see expecting commit
messages to include a reference to the issue number, and then it would
not be hard to adapt this program to key on that instead of matching
commit message texts.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
