Re: pgAdmin 1.0.2 Bundled...

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: Kurt Roeckx <Q(at)ping(dot)be>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: pgAdmin 1.0.2 Bundled...
Date: 2003-12-03 14:07:47
Views: Raw Message | Whole Thread | Download mbox
Lists: pgadmin-hackers

Dave Page wrote:

>>-----Original Message-----
>>From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
>>Sent: 03 December 2003 13:01
>>To: Dave Page
>>Cc: Kurt Roeckx; pgadmin-hackers(at)postgresql(dot)org
>>Subject: Re: [pgadmin-hackers] pgAdmin 1.0.2 Bundled...
>>CHANGELOG.txt could look like this, without release headers:
>> <li>2003-12-03 AP *** fix connect to MULE_INTERNAL db
>> <li>2003-12-02 AP fix acl property display
>> <li>2003-12-02 AP another fix closing Query Tool
>> <li>2003-12-01 AP add display of superuser
>>context settings
>> <li>2003-11-30 AP handle covering index for Foreign Keys
>> <li>2003-11-30 AP fix closing Query Tool while
>>query is running
>> <li>2003-11-30 AP fix error message when SET
>>client_encoding fails
>> <li>2003-11-26 AP 1.0.2 fix notice processing for
>> <li>2003-11-24 AP refactoring stats/depends:
>>populate on demand
>>--------------------------^^^^^ denotes the release version,
>> or *** if this patch is going
>>to trunk also.
>>Maybe we need release notes too, extracting all lines for
>>released versions.
>Hmm, so blank is trunk only, *** is trunk and stable branch, and <ver>
>indicates just a stable branch? Or have I misunderstood?
No, that's how it's meant.


In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Raphaƫl Enrici 2003-12-03 19:07:12 Re: Error message while connecting to a UNICODE
Previous Message Dave Page 2003-12-03 13:26:12 Re: pgAdmin 1.0.2 Bundled...