Thread: Going for Gold

Going for Gold

From
Andreas Pflug
Date:
Hi friends,

seems pgAdmin III 1.2RC is matured, should we make it Gold now? Tom Lane
promised to avoid further changes to the pgsql system schema, so
hopefully we won't face similar problems as with beta4->beta5 again.

As soon as pgsql8.0 is out, we can roll 1.2.1 to update the
documentation to the release version, but we shouldn't delay 1.2.0 for it.

Regards,
Andreas

Re: Going for Gold

From
Troels Arvin
Date:
On Mon, 29 Nov 2004 10:24:06 +0000, Andreas Pflug wrote:

> should we make it Gold now?

My vote: Yes - roll it.

--
Greetings from Troels Arvin, Copenhagen, Denmark


Re: Going for Gold

From
"Dave Page"
Date:

> -----Original Message-----
> From: pgadmin-hackers-owner@postgresql.org
> [mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of
> Andreas Pflug
> Sent: 29 November 2004 10:24
> To: pgadmin-hackers
> Subject: [pgadmin-hackers] Going for Gold
>
> Hi friends,
>
> seems pgAdmin III 1.2RC is matured, should we make it Gold
> now? Tom Lane promised to avoid further changes to the pgsql
> system schema, so hopefully we won't face similar problems as
> with beta4->beta5 again.
>
> As soon as pgsql8.0 is out, we can roll 1.2.1 to update the
> documentation to the release version, but we shouldn't delay
> 1.2.0 for it.

Sounds good to me. Are the docs/screenshots/pg docs etc up to date?

I can probably roll it tomorrow.... (following which I'll branch for
-patches)

/D

Re: Going for Gold

From
Andreas Pflug
Date:
Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: pgadmin-hackers-owner@postgresql.org
>>[mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of
>>Andreas Pflug
>>Sent: 29 November 2004 10:24
>>To: pgadmin-hackers
>>Subject: [pgadmin-hackers] Going for Gold
>>
>>Hi friends,
>>
>>seems pgAdmin III 1.2RC is matured, should we make it Gold
>>now? Tom Lane promised to avoid further changes to the pgsql
>>system schema, so hopefully we won't face similar problems as
>>with beta4->beta5 again.
>>
>>As soon as pgsql8.0 is out, we can roll 1.2.1 to update the
>>documentation to the release version, but we shouldn't delay
>>1.2.0 for it.
>
>
> Sounds good to me. Are the docs/screenshots/pg docs etc up to date?

Look ok for me.
>
> I can probably roll it tomorrow.... (following which I'll branch for
> -patches)

Lets go! 1.3 is waiting.

Regards,
Andreas