| From: | Mark Cave-Ayland <mark(dot)cave-ayland(at)ilande(dot)co(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: commitfest.postgresql.org is no longer fit for purpose |
| Date: | 2024-05-20 09:20:09 |
| Message-ID: | 366f4ccc-6d6f-4dcf-957b-c848d149c78c@ilande.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 20/05/2024 06:56, Mark Cave-Ayland wrote:
> In general you find that a series consists of 2 parts: 1) a set of refactorings to
> enable a new feature and 2) the new feature itself. Even if the details of 2) are
> still under discussion, often it is possible to merge 1) fairly quickly which also
> has the knock-on effect of reducing the size of later iterations of the series. This
> also helps with new contributors since having parts of the series merged sooner helps
> them feel valued and helps to provide immediate feedback.
[resend due to DKIM header failure]
Something else I also notice is that PostgreSQL doesn't have a MAINTAINERS or
equivalent file, so when submitting patches it's difficult to know who is expected to
review and/or commit changes to a particular part of the codebase (this is true both
with and without the CF system).
ATB,
Mark.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2024-05-20 09:34:32 | Re: PostgreSQL 17 Beta 1 release announcement draft |
| Previous Message | Aleksander Alekseev | 2024-05-20 09:20:02 | Re: Postgres and --config-file option |