| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, Michael Paquier <michael(at)paquier(dot)xyz>, David Steele <david(at)pgmasters(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Jeff Davis <pgsql(at)j-davis(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Commitfest manager for 2022-03 |
| Date: | 2022-03-19 20:35:05 |
| Message-ID: | 20220319203505.GT28503@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Feb 27, 2022 at 04:51:16PM +0800, Julien Rouhaud wrote:
> On Sat, Feb 26, 2022 at 06:37:21PM -0600, Justin Pryzby wrote:
> > Can I suggest to update the CF APP to allow:
> > | Target version: 16
> >
> > I also suggest to update patches to indicate which are (not) being considered
> > for v15.
>
> I don't really understand what that field is supposed to mean.
It can mean whatever we decide it's convenient for it to mean. I suppose its
primary purpose may have been to indicate which backbranch a bugfix applies to
(?)
I find it useful to indicate whether or not a patch is intended to be
considered for the next release. If a patch is targetting v15, it's more
interesting to review.
@Thomas Munro: I think it'd be useful if cfbot would also show 1) the "target
version" (if any); and, 2) whether a patch has a committer set.
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2022-03-19 21:46:13 | Re: Schema variables - new implementation for Postgres 15 |
| Previous Message | Alvaro Herrera | 2022-03-19 20:13:43 | Re: a misbehavior of partition row movement (?) |