Re: First draft of back-branch release notes is done

On 8/4/19 10:52 AM, Tom Lane wrote:
> "Jonathan S. Katz"  writes:
>> Perhaps instead of "June" it could be the specific version number (which
>> could cause some pain with the back branching?) or the "2019-06-20" release?
> 
> Putting in all the version numbers seems like a mess, but specifying
> 2019-06-20 would work --- or we could say "the most recent" minor
> releases?

That or "previous minor release" would seem to work.

(In the PR I'm putting in the versions it was introduced but we have the
luxury of only having one PR.)

Jonathan