| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Question about criteria for adding items to the v19 open items wiki page |
| Date: | 2026-04-23 05:28:23 |
| Message-ID: | 7A56B9A1-DC86-41BF-B171-7E6D68902CDA@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Apr 23, 2026, at 12:57, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Wednesday, April 22, 2026, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
> Please forgive this probably naive question, as this is the first release cycle I’ve experienced.
>
> I’ve seen people mention putting something on the v19 open items wiki page many times, but I’m not sure what kinds of things are supposed to go there. What should be added there, and are there any criteria for deciding that?
>
> Any bugs discovered in newly developed features in v19. As a practical matter, ones that seem complicated to resolve make it there since quickly resolved ones just get fixed.
>
> Bugs that reproduce in v18 or earlier would not be placed there.
>
> It’s a chance to demonstrate personal judgement. Severity and committer/author responsiveness are two additional criteria to judge. It’s both a simple tracker but also a kind of escalation channel since it gets RMT members involved.
>
> David J.
>
In the Open Issues section, I see the first item has no owner listed, so I assume we should add new items to the top of the list, and then, once they are confirmed, either an owner will be assigned, or the item will be moved to “Won’t Fix” or removed. Is that right?
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2026-04-23 05:32:43 | Re: [PATCH] Fix hashed ScalarArrayOp semantics for NULL LHS with non-strict comparators |
| Previous Message | Chao Li | 2026-04-23 05:22:04 | Re: Fix memory leak in postmasterMain |