> On 15 Sep 2017, at 17:19, Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Fri, Sep 15, 2017 at 10:15 AM, Daniel Gustafsson <daniel@yesql.se> wrote:
>> Have you had a chance to look at this such that we can expect a rebased version
>> of this patch during the commitfest?
>
> Frankly, I think things where there was a ping multiple weeks before
> the CommitFest started and no rebase before it started should be
> regarded as untimely submissions, and summarily marked Returned with
> Feedback. The CommitFest is supposed to be a time to get things that
> are ready before it starts committed before it ends. Some amount of
> back-and-forth during the CF is of course to be expected, but we don't
> even really have enough bandwidth to deal with the patches that are
> being timely updated, never mind the ones that aren’t.
I don’t necessarily disagree with this, and especially not the part about
bandwidth which is absolutely correct.
What has happened a lot however is that these patches have been moved to the
next CF, and possibly the next from there. In that scenario, if we can get the
patches rebased now they wont be in a worse state when pushed to the next
compared to if they bitrot further. That being said, perhaps we should move
closer to a model like what you describe, but thats for another thread to
discuss rather than threadjacking this one more IMO.
cheers ./daniel
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers