public inbox for [email protected]  

help / color / mirror / Atom feed

From: Daniel Gustafsson <[email protected]>
To: Jonathan S. Katz <[email protected]>
Cc: David Rowley <[email protected]>
Cc: [email protected]
Cc: Magnus Hagander <[email protected]>
Subject: Re: Typos in the featurematrix
Date: Thu, 23 Oct 2025 14:14:44 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<CAApHDvpOXAOPEhXRnWimyWmuRf+gN=yx22AoP_WM3aZ0M=n6Vw@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>

> On 23 Oct 2025, at 03:04, Jonathan S. Katz <[email protected]> wrote:

> * Going through 0001:
> 
> -    description: automatic invalidation of cached exceutions plans
> +    description: automatic invalidation of cached executions plans
> 
> should probably be "cached execution plans". Otherwise LGTM.

Fixed

> * Going through 0002:
> 
> -  - name: IN/OUT/INOUT parameters for pl/pgsql and PL/SQL
> +  - name: IN/OUT/INOUT parameters for PL/pgSQL and PL/SQL
> 
> We should probably not call it "PL/SQL" since it's not a procedural language. Perhaps:
> 
> -  - name: IN/OUT/INOUT parameters for pl/pgsql and PL/SQL
> +  - name: IN/OUT/INOUT parameters for PL/pgSQL and SQL stored functions

Fixed

>> The featurematrix was a rabbithole that went deep, looking closer I realized
>> that links were using a variety of target versions: /current/, /devel/, or the
>> version which was current at the time of adding.  This means that for old
>> features we we still linking to the 9.x version of the docs, which clearly
>> isn't helpful to our users.  We also had quite a few /static/ links which 301
>> redirects since we don't have that level anymore.
> 
> There were some reasons for this, the "version at the time of adding" ensuring that the links were accessible during the beta period (which also explained some of the /devel/, which I likely did). During the beta period, we'll still need to use the `/NN/` number so the links are accessible, but we can make it part of the procedure to more to `/current/` when we GA.

That makes a lot of sense.  We also need to use the /NN/ number for any feature
which is removed, to stabilise the link on the last version where it was
present.

Adding a "link-refresh" step to the GA checklist sounds like a good idea (and I
can volunteer to tackle it next time).

--
Daniel Gustafsson

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], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Typos in the featurematrix
  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