Horton
Menu

Re: Libxml2 load error on Windows

Alex Shulgin <ash@commandprompt.com>

View thread
From: Alex Shulgin <ash@commandprompt.com>
To: Dave Page <dpage@pgadmin.org>
Cc: Robert Haas <robertmhaas@gmail.com>, Talha Bin Rizwan <talha.rizwan@gmail.com>, pgsql-hackers@postgresql.org
Date: 2012-06-19T10:36:25Z
Lists: pgsql-hackers 
Dave Page <dpage@pgadmin.org> writes:

> On Tue, Jun 19, 2012 at 11:04 AM, Alex Shulgin <ash@commandprompt.com> wrote:
>>
>> 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.)
>
> Well yes, but the point is that that is not how the project works. I'm
> asking how we do handle this problem at the moment, because I realised
> I haven't seen this happen in the past (largely because I haven't been
> paying attention).

It only works as long as there is some mechanism to ensure that the bugs
which were not submitted to commitfest are looked at.  If there is no,
then it doesn't work actually.

So is there a real and reliable mechanism for that?

--
Alex

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Check LIBXML_VERSION instead of testing in configure script.