Re: 9.2 branch and 9.1beta2 timing (was Re: InitProcGlobal cleanup)

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: 9.2 branch and 9.1beta2 timing (was Re: InitProcGlobal cleanup)
Дата
Msg-id BANLkTik_Siy4EAXf73mdp0qX40QreZQvHA@mail.gmail.com
обсуждение исходный текст
Ответ на 9.2 branch and 9.1beta2 timing (was Re: InitProcGlobal cleanup)  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: 9.2 branch and 9.1beta2 timing (was Re: InitProcGlobal cleanup)  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Список pgsql-hackers
On Thu, Jun 2, 2011 at 4:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> I'll commit this to 9.2 after we branch.  (When are we doing that, BTW?)
>
> Sometime in the next two weeks I guess ;-).  At the PGCon meeting we
> said 1 June, but seeing that we still have a couple of open beta2 issues
> I'm not in a hurry.
>
> I think a reasonable plan would be to fix the currently known open
> issues, push out a beta2, and then branch.  That would avoid
> double-patching.  We'd want to get this done before the commitfest
> starts on the 15th, of course, so if we stick to usual release
> scheduling that would mean wrap next Thursday (June 9), beta2 announce
> on Monday the 13th, and make the branch somewhere around that date as
> well.
>
> Comments?

OK by me.  It appears that the open items list is a bit stale:

http://wiki.postgresql.org/wiki/PostgreSQL_9.1_Open_Items

The first item listed there is, I believe, fixed.  I'm not sure about
the second.  You just volunteered to fix the third, and the fourth is
awaiting comments on -bugs.  The larger problem is that there are
likely some other things that should be listed there, but aren't.  If
anyone is aware of stuff we need to get done, please add it there...

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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Ross J. Reedstrom"
Дата:
Сообщение: Re: BLOB support
Следующее
От: "Kevin Grittner"
Дата:
Сообщение: Re: SSI predicate locking on heap -- tuple or row?