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:36:25
Message-ID: 87obofziza.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 11:04 AM, Alex Shulgin <ash(at)commandprompt(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Boszormenyi Zoltan 2012-06-19 11:13:26 Re: [PATCH] lock_timeout and common SIGALRM framework
Previous Message Dave Page 2012-06-19 10:27:31 Re: Libxml2 load error on Windows