commitfest app bug/feature

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: commitfest app bug/feature
Date: 2015-05-07 19:17:04
Message-ID: alpine.DEB.2.10.1505072057420.20788@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello,

Some comments/bug report about the commitfest web app which just bite
me:-)

When creating a patch with the commitfest app, if the thread does not
exist the application seems to reject the creation, so you may resubmit
because you know the thread is going to exist soon... Well, this is a bad
idea:-)

Indeed the first submission, although it looked like it had failed, has
really been created anyway, and the resubmission creates another entry. If
you click again, you get a third. And so on.

Maybe the description should be unique at least per commitfest?

Then there is no way to remove a patch from the application. You end up
marking them as "Rejected", which does not make much sense, see the bottom
of the 2015-06 commitfest list...

Maybe a "Duplicate" status would be better, and the ability to actually
remove a stupid entry would be even nicer, although maybe not desirable,
ot sure. And/or some way to prevent duplicates based on the description...

--
Fabien.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2015-05-07 19:41:13 Re: Auditing extension for PostgreSQL (Take 2)
Previous Message Bruce Momjian 2015-05-07 19:00:49 Re: Disabling trust/ident authentication configure option