Re: Libxml2 load error on Windows - Mailing list pgsql-hackers

From Alex Shulgin
Subject Re: Libxml2 load error on Windows
Date
Msg-id 871ulb1ut3.fsf@commandprompt.com
Whole thread Raw
In response to Re: Libxml2 load error on Windows  (Dave Page <dpage@pgadmin.org>)
Responses Re: Libxml2 load error on Windows  (Dave Page <dpage@pgadmin.org>)
List pgsql-hackers
Dave Page <dpage@pgadmin.org> writes:

> On Tue, Jun 19, 2012 at 4:43 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>>
>>
>> Please add this patch here so that it doesn't get lost in the shuffle:
>>
>> https://commitfest.postgresql.org/action/commitfest_view/open
>
> Hmm, that raises an interesting question (though maybe I've just
> missed this happening in the past). This is a bug fix, that we'll want
> in the next back branch updates, not just 9.3. Sticking it in the open
> commit fest means it may well not get looked at for 2-3 months or so.
> How do we prevent that happening?

In a real bug-tracking system we would create a new bug/ticket and set
it's target version to 'candidate for next minor release' or something
like that.  This way, if we don't release unless all targeted bugs are
resolved, this would be taken care of (hopefully.)


pgsql-hackers by date:

Previous
From: "Etsuro Fujita"
Date:
Subject: Re: [PATCH] Lazy hashaggregate when no aggregation is needed
Next
From: Dave Page
Date:
Subject: Re: Libxml2 load error on Windows