public inbox for [email protected]
help / color / mirror / Atom feedFrom: Joe Conway <[email protected]>
To: PostgreSQL-development <[email protected]>
Subject: question regarding policy for patches to out-of-support branches
Date: Wed, 5 Jun 2024 14:07:40 -0400
Message-ID: <[email protected]> (raw)
I was having a discussion regarding out-of-support branches and effort
to keep them building, but could not for the life of me find any actual
documented policy (although I distinctly remember that we do something...).
I did find fleeting references, for example:
8<-----------------------
commit c705646b751e08d584f6eeb098f1ed002aa7b11c
Author: Tom Lane <[email protected]>
Date: 2022-09-21 13:52:38 -0400
<snip>
Per project policy, this is a candidate for back-patching into
out-of-support branches: it suppresses annoying compiler warnings
but changes no behavior. Hence, back-patch all the way to 9.2.
8<-----------------------
and on its related thread:
8<-----------------------
However, I think that that would *not* be fit material for
back-patching into out-of-support branches, since our policy
for them is "no behavioral changes".
8<-----------------------
Is the policy written down somewhere, or is it only project lore? In
either case, what is the actual policy?
Thanks,
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: question regarding policy for patches to out-of-support branches
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox