From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Trac tickets |
Date: | 2010-12-31 15:19:10 |
Message-ID: | AANLkTinakobsVdA0bhDJhjPmjsnWudDj2ukynqNJ7Ryi@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Fri, Dec 31, 2010 at 3:09 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Fri, Dec 31, 2010 at 16:07, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> On Fri, Dec 31, 2010 at 3:03 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> Actually, I take it back.
>>>
>>> The CHANGELOG on the REL-1_12_PATCHES has some changes for 1.12.1,
>>> 1.12.2, 1.12.3. And surprisingly enough also 1.14.0, which certainly
>>> didn't exist back then...
>>
>> Yes - we've done it that way for years.
>
> I know - and it's been itching me for years ;)
>
>
>>> Which kind of proves my point about the confusion;)
>>
>> Meh. Someone committed a bad merge. The doesn't mean it hasn't worked
>> for the most part.
>
> So, just to be clear:
>
> Something that's backpatched goes into both master and the backpatch CHANGELOG.
>
> And the order in the CHANGELOG is chronological, *not*
> version-ordered? (resulting in mixed versions in head, but consistent
> version ordering in backbranches)?
Yes.
And for the record - I find it a PITA too; but... it's *much* easier
for me than trying to find another few hours for additional tedious
release prep tasks.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2010-12-31 15:24:13 | Re: Email notification pgAgent |
Previous Message | Magnus Hagander | 2010-12-31 15:09:38 | Re: Trac tickets |