| From: | "Markus Wanner" <markus(at)bluegap(dot)ch> |
|---|---|
| To: | "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com> |
| Cc: | "Marko Kreen" <markokr(at)gmail(dot)com>, "Greg Stark" <stark(at)enterprisedb(dot)com>, "Andres Freund" <andres(at)anarazel(dot)de>, "Aidan Van Dyk" <aidan(at)highrise(dot)ca>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Magnus Hagander" <magnus(at)hagander(dot)net>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Developer meeting minutes up |
| Date: | 2009-06-05 07:05:14 |
| Message-ID: | 20090605090514.11712ntlvhi2deay@mail.bluegap.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Quoting "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>:
> Seems you'd want to do is create a new branch as close to the point
> where the bug was introduced - and then merge that forward into each
> of the branches.
Thank you for pointing this out. As a fan of monotone I certainly know
and like that way. However, for people who are used to CVS, lots of
branching and merging quickly sound dangerous and messy. So I'd like
to keep things as simple as possible while still keeping possibilities
open for the future.
Note that a requirement for daggy fixes is that "the bug is fixed
close to the point where it was introduced". So fixing it on the
oldest stable branch that introduced a bug instead of fixing it on
HEAD and then back-porting would certainly be a step into the right
direction. And I think it would be sufficient in most cases. If not,
we can still enhance that and used daggy fixes later on (as long as we
have a conversion that allows merging, that is).
Regards
Markus Wanner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yoshinori Sano | 2009-06-05 07:18:29 | Simple, safe hot backup and recovery |
| Previous Message | Fujii Masao | 2009-06-05 06:14:29 | Re: postmaster recovery and automatic restart suppression |