Re: commit fest status and release timeline

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: commit fest status and release timeline
Дата
Msg-id CABUevExzqauqVSKCEwO+wDm1t+2051P4XwbeMD-Wk6-RmKwhrw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: commit fest status and release timeline  (Tomas Vondra <tv@fuzzy.cz>)
Список pgsql-hackers
On Mon, Mar 3, 2014 at 4:34 PM, Tomas Vondra <tv@fuzzy.cz> wrote:
On 1.3.2014 18:01, Peter Eisentraut wrote:
> Status Summary. Needs Review: 36, Waiting on Author: 7, Ready for
> Committer: 16, Committed: 43, Returned with Feedback: 8, Rejected:
> 4. Total: 114.
>
> We're still on track to achieve about 50% committed patches, which
> would be similar to the previous few commit fests. So decent job so
> far.

I'm wondering what is the best way to select a patch to review. I mean,
there are many patches with "needs review" (and often no reviewer) just
one or two comments, but when I checked the email archives there's often
a lot people discussing it.

Do we have a list of patches that didn't get a proper review yet / badly
need another one?

What about improving the commitfest page by displaying a number of
related e-mail messages / number of people involved? Shouldn't be
difficult to get this from the mail archives ...

I have some code for that part, that needs a coupe of rounds of final hacking and polish. I've had many targets for it, but right now the target is to be done before pgcon, so we can put it in play for the next set of commitfests. It's not going to happen for *this* one, and we don't want to distrupt the flow even more by making big changes to the tooling in the middle of it.

That said, there is definitely a need :) 

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Changeset Extraction v7.9
Следующее
От: Fabrízio de Royes Mello
Дата:
Сообщение: GSoC proposal - "make an unlogged table logged"