Thread: Propose Beta3 for July
Folks,
There have been quite a number of fixes since Beta2. If we're going to
make a summer release date at all, we need to get moving.
Therefore, I propose that we set a beta3 release date for July 8th.
That should give it enough space from the American Holiday.
This would imply, of course, that we're going to go ahead an accept
Simon's patches for Keepalive, since we don't see to have any others.
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com
Josh Berkus <josh@agliodbs.com> writes:
> Therefore, I propose that we set a beta3 release date for July 8th.
> That should give it enough space from the American Holiday.
You mean wrap on Thursday the 8th for release on Monday the 12th?
That'd be fine with me. Actual release on the 8th would mean asking
people to do release prep work when they should be out watching
fireworks.
regards, tom lane
On 6/28/10 11:40 AM, Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
>> Therefore, I propose that we set a beta3 release date for July 8th.
>> That should give it enough space from the American Holiday.
>
> You mean wrap on Thursday the 8th for release on Monday the 12th?
> That'd be fine with me. Actual release on the 8th would mean asking
> people to do release prep work when they should be out watching
> fireworks.
Yes. I'll need to recruit someone else for the announcement (I'll be in
transit on the 12th) but that's easy.
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com
Why not do prep work with a release on the 5th? On Mon, 28 Jun 2010, Tom Lane wrote: > Josh Berkus <josh@agliodbs.com> writes: >> Therefore, I propose that we set a beta3 release date for July 8th. >> That should give it enough space from the American Holiday. > > You mean wrap on Thursday the 8th for release on Monday the 12th? > That'd be fine with me. Actual release on the 8th would mean asking > people to do release prep work when they should be out watching > fireworks. > > regards, tom lane > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy@hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org
On 6/28/10 11:52 AM, Marc G. Fournier wrote:
>
> Why not do prep work with a release on the 5th?
I think that a bunch of the people needed for wraps are Americans. No?
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com
Josh Berkus <josh@agliodbs.com> writes:
> On 6/28/10 11:52 AM, Marc G. Fournier wrote:
>> Why not do prep work with a release on the 5th?
> I think that a bunch of the people needed for wraps are Americans. No?
In any case, you won't get much attention for an announcement on the
5th. Better to wait a week.
regards, tom lane
On Mon, 28 Jun 2010, Josh Berkus wrote: > On 6/28/10 11:52 AM, Marc G. Fournier wrote: >> >> Why not do prep work with a release on the 5th? > > I think that a bunch of the people needed for wraps are Americans. No? I'm not sure of all our nationalities .. I'm in Canada, Dave is in EU ... I *think* the FreeBSD ports maintainer is also in the EU ... Devrim is ... ? ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy@hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org
On Mon, Jun 28, 2010 at 2:56 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Josh Berkus <josh@agliodbs.com> writes: >> On 6/28/10 11:52 AM, Marc G. Fournier wrote: >>> Why not do prep work with a release on the 5th? > >> I think that a bunch of the people needed for wraps are Americans. No? > > In any case, you won't get much attention for an announcement on the > 5th. Better to wait a week. At PGCon, the plan we discussed was to branch the tree on 7/1 and start the next CommitFest on 7/15. If beta3 is going to happen relatively close to the beginning of July, it might make sense to create the new branch just after we wrap beta3. But if we're not going to wrap beta3 until mid-July, then we need another plan. But I *really* don't want to wait that long. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
Robert Haas <robertmhaas@gmail.com> writes:
> At PGCon, the plan we discussed was to branch the tree on 7/1 and
> start the next CommitFest on 7/15. If beta3 is going to happen
> relatively close to the beginning of July, it might make sense to
> create the new branch just after we wrap beta3.
Seems reasonable. The 7/1 date was never set in stone anyway.
regards, tom lane
> At PGCon, the plan we discussed was to branch the tree on 7/1 and
> start the next CommitFest on 7/15. If beta3 is going to happen
> relatively close to the beginning of July, it might make sense to
> create the new branch just after we wrap beta3. But if we're not
> going to wrap beta3 until mid-July, then we need another plan. But I
> *really* don't want to wait that long.
Well, do you consider 7/8 to be mid-July or "close to the beginning"?
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com
On Mon, Jun 28, 2010 at 3:23 PM, Josh Berkus <josh@agliodbs.com> wrote: > >> At PGCon, the plan we discussed was to branch the tree on 7/1 and >> start the next CommitFest on 7/15. If beta3 is going to happen >> relatively close to the beginning of July, it might make sense to >> create the new branch just after we wrap beta3. But if we're not >> going to wrap beta3 until mid-July, then we need another plan. But I >> *really* don't want to wait that long. > > 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. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
> 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
On Mon, Jun 28, 2010 at 3:32 PM, Josh Berkus <josh@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
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Jun 28, 2010 at 3:23 PM, Josh Berkus <josh@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
On Mon, Jun 28, 2010 at 3:44 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Robert Haas <robertmhaas@gmail.com> writes: >> On Mon, Jun 28, 2010 at 3:23 PM, Josh Berkus <josh@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
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Jun 28, 2010 at 3:44 PM, Tom Lane <tgl@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
Josh Berkus wrote: > Folks, > > There have been quite a number of fixes since Beta2. If we're going to > make a summer release date at all, we need to get moving. > > Therefore, I propose that we set a beta3 release date for July 8th. > That should give it enough space from the American Holiday. > > This would imply, of course, that we're going to go ahead an accept > Simon's patches for Keepalive, since we don't see to have any others. FYI, if we are lucky, we have time for a beta3 and beta4 before we have to start planning for RC1. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. +