Re: Commitfest 2023-03 starting tomorrow!

From: "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>
To: "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commitfest 2023-03 starting tomorrow!
Date: 2023-04-09 01:45:04
Message-ID: CAM-w4HNFOvzUhB9BZyAzkf4tOmNE3OVfzAd1hqncThLd27xR8g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 8 Apr 2023 at 11:37, Greg Stark <stark(at)mit(dot)edu> wrote:
>
> c) Pick out the Bug Fixes, cleanup patches, and other non-feature
> patches that might be open issues for v16.

So on further examination it seems there are multiple category of
patches that are worth holding onto rather than shifting to the next
release:

* Bug Fixes
* Documentation patches
* Build system patches, especially meson-related patches
* Testing patches, especially if they're testing new features
* Patches that are altering new features that were committed in this release

Some of these, especially the last category, are challenging for me to
determine. If I move forward a patch of yours that you think makes
sense to treat as an open issue that should be resolved in this
release then feel free to say.

--
Gregory Stark
As Commitfest Manager

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-04-09 01:50:49 Re: Commitfest 2023-03 starting tomorrow!
Previous Message Greg Stark 2023-04-09 01:24:46 Re: Proposal: %T Prompt parameter for psql for current time (like Oracle has)