Re: commitfest.postgresql.org is no longer fit for purpose - Mailing list pgsql-hackers

From Joe Conway
Subject Re: commitfest.postgresql.org is no longer fit for purpose
Date
Msg-id d28897bf-8374-45d0-9bc3-8ed05c412b61@joeconway.com
Whole thread Raw
In response to Re: commitfest.postgresql.org is no longer fit for purpose  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: commitfest.postgresql.org is no longer fit for purpose
Re: commitfest.postgresql.org is no longer fit for purpose
List pgsql-hackers
On 5/16/24 16:57, Jacob Champion wrote:
> On Thu, May 16, 2024 at 1:31 PM Joe Conway <mail@joeconway.com> wrote:
>> Maybe we should just make it a policy that *nothing* gets moved forward
>> from commitfest-to-commitfest and therefore the author needs to care
>> enough to register for the next one?
> 
> I think that's going to severely disadvantage anyone who doesn't do
> this as their day job. Maybe I'm bristling a bit too much at the
> wording, but not having time to shepherd a patch is not the same as
> not caring.

Maybe the word "care" was a poor choice, but forcing authors to think 
about and decide if they have the "time to shepherd a patch" for the 
*next CF* is exactly the point. If they don't, why clutter the CF with it.

-- 
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
Next
From: Andrew Dunstan
Date:
Subject: Re: Why is citext/regress failing on hamerkop?