| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Commit fest 2017-11 |
| Date: | 2018-05-22 17:57:22 |
| Message-ID: | CA+Tgmoahsh4GQPMMRcN6+RcB1v1Pzi0X6WJL0OxnO5swTvriow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 29, 2018 at 4:19 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> I wonder if we should consider adding a field to the CF app *specifically*
> to track things like this. What I'm thinking is a field that's set (or at
> least verified) by the person who flags a patch as committed with choices
> like Trivial/Simple/Medium/Complex (trivial being things like typo fixes
> etc, which today can hugely skew the stats).
I think this would be pretty subjective ... and there are also a LOT
of patches that don't go through the CF process. The ratio of commits
to commitfest entries is at least 5:1. If we only track what gets
registered in the CF app we're ignoring a huge amount of stuff.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2018-05-22 17:59:29 | Re: Commit fest 2017-11 |
| Previous Message | Andres Freund | 2018-05-22 16:57:15 | Re: found xmin from before relfrozenxid on pg_catalog.pg_authid |