Обсуждение: Release announcement drafts?

I have seen for years that this mailing list has been used around a month before 
public release of a new major Postgres version to solicit feedback on release 
announcement drafts, including related marketing. Not that I typically replied 
personally, but its been a pattern I looked at for years. With 2 days to go, I 
did not see any such postings. Is the draft feedback now taking place in other 
forums instead, or is this year's just going to be sent without soliciting 
feedback first? -- Darren Duncan

Hi Darren,

On 9/23/25 12:38 PM, Darren Duncan wrote:
> I have seen for years that this mailing list has been used around a 
> month before public release of a new major Postgres version to solicit 
> feedback on release announcement drafts, including related marketing. 
> Not that I typically replied personally, but its been a pattern I looked 
> at for years. With 2 days to go, I did not see any such postings. Is the 
> draft feedback now taking place in other forums instead, or is this 
> year's just going to be sent without soliciting feedback first? -- 

I had posted on -hackers[1] to solicit feedback. There had previously 
been overlap in the feedback coming from both places and I wanted to try 
to consolidate it to avoid the "split-brain" problem. However, if this 
is an issue, for the next cycle I can continue to post the announcement 
on -advocacy + -hackers for feedback.

Thanks,

Jonathan

[1] 
https://www.postgresql.org/message-id/076eced4-5d97-4b2f-9554-6859088c5ef3%40postgresql.org

On 9/23/25 11:46, Jonathan S. Katz wrote:
> Hi Darren,
> 
> On 9/23/25 12:38 PM, Darren Duncan wrote:

> 
> I had posted on -hackers[1] to solicit feedback. There had previously 
> been overlap in the feedback coming from both places and I wanted to try 
> to consolidate it to avoid the "split-brain" problem. However, if this 
> is an issue, for the next cycle I can continue to post the announcement 
> on -advocacy + -hackers for feedback.

This directly relates to advocacy, so yes it should be posted here also. 
There are plenty of people that don't want to deal with the fire hose 
that is -hackers, yet want to and are capable of spreading the word.

> 
> Thanks,
> 
> Jonathan
> 
> [1] https://www.postgresql.org/message- 
> id/076eced4-5d97-4b2f-9554-6859088c5ef3%40postgresql.org
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com

> On 9/23/25 11:46, Jonathan S. Katz wrote:
>> Hi Darren,
>>
>> On 9/23/25 12:38 PM, Darren Duncan wrote:
>
>>
>> I had posted on -hackers[1] to solicit feedback. There had previously
>> been overlap in the feedback coming from both places and I wanted to
>> try to consolidate it to avoid the "split-brain" problem. However, if
>> this is an issue, for the next cycle I can continue to post the
>> announcement on -advocacy + -hackers for feedback.
>
> This directly relates to advocacy, so yes it should be posted here also.
> There are plenty of people that don't want to deal with the fire hose
> that is -hackers, yet want to and are capable of spreading the word.

Agreed.


--
Cédric Villemain +33 6 20 30 22 52
https://www.Data-Bene.io
PostgreSQL Support, Expertise, Training, R&D

Hi,

On 9/25/25 12:38 PM, Umair Shahid wrote:
> 
> 
> On Wed, Sep 24, 2025 at 12:36 AM Adrian Klaver 
> <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
> 
>     On 9/23/25 11:46, Jonathan S. Katz wrote:
>      > Hi Darren,
>      >
>      > On 9/23/25 12:38 PM, Darren Duncan wrote:
> 
>      >
>      > I had posted on -hackers[1] to solicit feedback. There had
>     previously
>      > been overlap in the feedback coming from both places and I wanted
>     to try
>      > to consolidate it to avoid the "split-brain" problem. However, if
>     this
>      > is an issue, for the next cycle I can continue to post the
>     announcement
>      > on -advocacy + -hackers for feedback.
> 
>     This directly relates to advocacy, so yes it should be posted here
>     also.
>     There are plenty of people that don't want to deal with the fire hose
>     that is -hackers, yet want to and are capable of spreading the word.
> 
> 
> +1

Thanks for the feedback. There are two separate points where I'd like to 
address:

* Soliciting feedback ahead of the release. I agree with these points, 
and I apologize for my oversight. I (or whoever handles the release) 
will ensure we post it here ahead of the GA next year. Please accept my 
apologies.

* Spreading the word: I appreciate the willingness and sentiment of 
doing this as this is a big part of helping to grow the community. I 
think this is independent of the first point, as this is a continuous 
process, and with a new release, the big efforts largely start after the 
GA is available (such as today[1]).

Thanks,

Jonathan

[1] https://www.postgresql.org/about/news/postgresql-18-released-3142/