Re: "rejected" vs "returned with feedback" in new CF app - Mailing list pgsql-hackers

From Robert Haas
Subject Re: "rejected" vs "returned with feedback" in new CF app
Date
Msg-id 71EDE632-3816-4A81-A3EF-4CF642B2445B@gmail.com
Whole thread Raw
In response to Re: "rejected" vs "returned with feedback" in new CF app  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Apr 9, 2015, at 5:50 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> The problem with the whole thing is that you're asking the person doing
> the "returned" marking to guess whether the patch will be resubmitted in
> a future CF.
>
> The right workflow here, IMO, is that a patch should be marked returned or
> rejected, full stop; and then when/if the author submits a new version for
> a future CF, there should be a way *at that time* to re-link the email
> thread into that future CF.

Yeah, or a way to reactivate the old entry at that time.  Any kind of routine carryover to the next CF is going to lead
toan accumulation of dead patches with live CF entries; it should require some action to re-enter a previously returned
patchin the latest CF. 

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: FPW compression leaks information
Next
From: Michael Paquier
Date:
Subject: Re: Supporting TAP tests with MSVC and Windows