Re: question regarding policy for patches to out-of-support branches

On 6/6/24 14:12, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, Jun 6, 2024 at 4:25 AM Hannu Krosing <hannuk(at)google(dot)com> wrote:
>>> Not absolutely sure, but would at least adding a page to PostgreSQL
>>> Wiki about this make sense ?
>
>> I feel like we need to do something. Tom says this is a policy, and
>> he's made that comment before about other things, but the fact that
>> they're not memorialized anywhere is a huge problem, IMHO.
>
> I didn't say it wasn't ;-)
>
> ISTM we have two basic choices: wiki page, or new SGML docs section.
> In the short term I'd lean to a wiki page. It'd be reasonable for
>
> https://wiki.postgresql.org/wiki/Committing_checklist
>
> to link to it (and maybe the existing section there about release
> freezes would be more apropos on a "Project policies" page? Not
> sure.)
>
> To get a sense of how much of a problem we have, I grepped the git
> history for comments mentioning project policies. Ignoring ones
> that are really talking about very localized issues, what I found
> is attached. It seems like it's little enough that a single wiki
> page with subsections ought to be enough. I'm not super handy with
> editing the wiki, plus I'm only firing on one cylinder today (seem
> to have acquired a head cold at pgconf), so maybe somebody else
> would like to draft something?

I added them here with minimal copy editing an no attempt to organize or
sort into groups:

https://wiki.postgresql.org/wiki/Committing_checklist#Policies

If someone has thoughts on how to improve I am happy to make more changes.

--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com