Re: rc1 or beta4?
От | Dave Page |
---|---|
Тема | Re: rc1 or beta4? |
Дата | |
Msg-id | CA+OCxoxLMAuGwrcPBaVAz8P=pCtHh5mKwzSG=VqDp=c5Sij=QQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: rc1 or beta4? (Thom Brown <thom@linux.com>) |
Ответы |
Re: rc1 or beta4?
|
Список | pgsql-hackers |
On Wed, Aug 17, 2011 at 5:16 PM, Thom Brown <thom@linux.com> wrote: > On 17 August 2011 16:56, Jan Urbański <wulczer@wulczer.org> wrote: >> >> On 17/08/11 17:50, Thom Brown wrote: >> > On 17 August 2011 16:47, Jan Urbański <wulczer@wulczer.org> wrote: >> > >> >> On 17/08/11 15:00, Dave Page wrote: >> >>> The current plan (or, the last one I recall) is to push another 9.1 >> >>> release tomorrow, for Monday release. Are we going with beta4 or rc1? >> >> >> >> Sorry to butt in, but it would probably be good to include fixes for >> >> the >> >> two segfault plpython bugs[1] before wrapping up the release. >> >> >> > >> > It's not listed as a beta-blocker yet. I take it that it should? >> >> Oh, in the wiki? I don't know, it is a segfault-causing bug, but all I >> wanted was to draw some attention in case the people wrapping the >> release missed that thread. > > It was my understanding that the only things which can prevent a new beta or > release candidate are listed on the wiki > (http://wiki.postgresql.org/wiki/PostgreSQL_9.1_Open_Items). There's only > one item on the list now, and I think even that has probably been fixed. If > it's not on there, I guess it hasn't yet been considered to be something > which can block a release. Since it's not even listed as a non-blocker > either, I don't think it's been reviewed in this context. That doesn't mean other things can't or shouldn't be fixed - just that they won't necessarily cause adjustment of the schedule to accomodate them. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: