Prev: [HACKERS] Propose Beta3 for July
Next: Keepalives win32
From: Josh Berkus on 28 Jun 2010 15:32

> 7/8 would be about the last date I'd consider reasonable, given a CF
> starting 7/15. I would prefer a few days earlier, but I'm not sure
> how much of a vote I get considering that I'm not actively involved in
> the release process or the packaging of installers.

Well, I think realistically we could wrap earlier and release on the 7th
or 8th. That just depends on being able to do the wrap with a 100%
non-US (as in, no Bruce or Tom) team. I don't see that as impossible,
but then I'm not involved in wrapping either.

--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Robert Haas on 28 Jun 2010 15:41
On Mon, Jun 28, 2010 at 3:32 PM, Josh Berkus <josh(a)agliodbs.com> wrote:
>> 7/8 would be about the last date I'd consider reasonable, given a CF
>> starting 7/15. �I would prefer a few days earlier, but I'm not sure
>> how much of a vote I get considering that I'm not actively involved in
>> the release process or the packaging of installers.
>
> Well, I think realistically we could wrap earlier and release on the 7th
> or 8th. �That just depends on being able to do the wrap with a 100%
> non-US (as in, no Bruce or Tom) team. �I don't see that as impossible,
> but then I'm not involved in wrapping either.

I don't know what all the steps are. I can certainly tag and bundle
if that's helpful... my first try (alpha5) got the tags right and the
bundling wrong, but I think I know how to do it. But before that we
have to get all the fixes in, and after that someone needs to build
installers and RPMs, distribute things through the mirror network,
etc. and I don't know how all that works.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on 28 Jun 2010 15:44
Robert Haas <robertmhaas(a)gmail.com> writes:
> On Mon, Jun 28, 2010 at 3:23 PM, Josh Berkus <josh(a)agliodbs.com> wrote:
>> Well, do you consider 7/8 to be mid-July or "close to the beginning"?

> 7/8 would be about the last date I'd consider reasonable, given a CF
> starting 7/15. I would prefer a few days earlier, but I'm not sure
> how much of a vote I get considering that I'm not actively involved in
> the release process or the packaging of installers.

It would be better not to branch until we're certain we won't need to
re-wrap the beta. I'm wondering why you see a need for any daylight at
all between the branch date and the start of the CF.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Robert Haas on 28 Jun 2010 15:51
On Mon, Jun 28, 2010 at 3:44 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas(a)gmail.com> writes:
>> On Mon, Jun 28, 2010 at 3:23 PM, Josh Berkus <josh(a)agliodbs.com> wrote:
>>> Well, do you consider 7/8 to be mid-July or "close to the beginning"?
>
>> 7/8 would be about the last date I'd consider reasonable, given a CF
>> starting 7/15. �I would prefer a few days earlier, but I'm not sure
>> how much of a vote I get considering that I'm not actively involved in
>> the release process or the packaging of installers.
>
> It would be better not to branch until we're certain we won't need to
> re-wrap the beta. �I'm wondering why you see a need for any daylight at
> all between the branch date and the start of the CF.

Well, I guess it isn't technically necessary, but I think it might
make things less hectic. Last year we had two weeks, which was more
than we needed, but I think a little slack time will make things go
more smoothly.

BTW, if we're going to do a second pgindent run for this release, we
probably want to do that before the branch point. Not sure if it
should be done before or after beta3.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on 28 Jun 2010 15:59
Robert Haas <robertmhaas(a)gmail.com> writes:
> On Mon, Jun 28, 2010 at 3:44 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
>> It would be better not to branch until we're certain we won't need to
>> re-wrap the beta. �I'm wondering why you see a need for any daylight at
>> all between the branch date and the start of the CF.

> Well, I guess it isn't technically necessary, but I think it might
> make things less hectic. Last year we had two weeks, which was more
> than we needed, but I think a little slack time will make things go
> more smoothly.

I don't want to do it on the same day or anything like that, but I think
a couple days slack is plenty.

> BTW, if we're going to do a second pgindent run for this release, we
> probably want to do that before the branch point. Not sure if it
> should be done before or after beta3.

Yes, we must do that before branching. My preference would be to do it
before the beta --- I still feel there's a nonzero chance of pgindent
breaking things, so testing should happen on post-pgindent code.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: [HACKERS] Propose Beta3 for July
Next: Keepalives win32