| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: commitfest.postgresql.org is no longer fit for purpose |
| Date: | 2024-05-17 07:03:51 |
| Message-ID: | b8297a34-d92f-4646-82e7-98a1d1b5a0da@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17/05/2024 08:05, Peter Eisentraut wrote:
> On 17.05.24 04:26, Robert Haas wrote:
>> I do*emphatically* think we need a parking lot.
>
> People seem to like this idea; I'm not quite sure I follow it. If you
> just want the automated patch testing, you can do that on your own by
> setting up github/cirrus for your own account. If you keep emailing the
> public your patches just because you don't want to set up your private
> testing tooling, that seems a bit abusive?
Agreed. Also, if you do want to park a patch in the commitfest, setting
it to "Waiting on Author" is effectively that.
I used to add patches to the commitfest to run CFBot on them, but some
time back I bit the bullet and set up github/cirrus to run on my own
github repository. I highly recommend that. It only takes a few clicks,
and the user experience is much better: push a branch to my own github
repository, and cirrus CI runs automatically.
--
Heikki Linnakangas
Neon (https://neon.tech)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2024-05-17 07:19:20 | Re: Incorrect Assert in BufFileSize()? |
| Previous Message | Yasir | 2024-05-17 06:48:17 | Re: Ignore Visual Studio's Temp Files While Working with PG on Windows |