Re: Libxml2 load error on Windows

From: Alex Shulgin <ash(at)commandprompt(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Talha Bin Rizwan <talha(dot)rizwan(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Libxml2 load error on Windows
Date: 2012-06-19 10:04:56
Message-ID: 871ulb1ut3.fsf@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Dave Page <dpage(at)pgadmin(dot)org> writes:

> On Tue, Jun 19, 2012 at 4:43 AM, Robert Haas <robertmhaas(at)gmail(dot)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.)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2012-06-19 10:27:31 Re: Libxml2 load error on Windows
Previous Message Etsuro Fujita 2012-06-19 09:41:49 Re: [PATCH] Lazy hashaggregate when no aggregation is needed