From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | PostgreSQL Advocacy <pgsql-advocacy(at)lists(dot)postgresql(dot)org> |
Subject: | PostgreSQL 12 Press Release - First Draft |
Date: | 2019-08-21 20:43:02 |
Message-ID: | c56eeb88-4a8c-2c6c-b5f1-9d46872c247c@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
Hi,
Attached is a first draft of the press release for PostgreSQL 12.
Feedback welcome (more below), though I ask feedback to be provided no
later than September 6, 2019.
A few comments for context:
Using the release notes[1], 12 beta 1 release[2], and miscellaneous
feedback as a guide, there seemed to be roughly five major feature groups:
- Overall Performance Improvements (focuses on the indexing +
partitioning work, MCV stats)
- Enhancements to SQL Conformance & Functionality (SQL/JSON, inlined
CTEs, generated columns)
- Internationalization (ICU case insensitivity)
- Authentication (GSSAPI encryption, LDAP discovery, clientcert=verify-full)
- Administrative (REINDEX CONCURRENTLY, pg_checksums)
I mentioned pluggable storage interface in it but did not elaborate in
too much detail. I am a huge fan of this effort, but for the typical
PG12 user, we may not want to elaborate too much on it in the general
press release.
Feedback I'm looking for:
- Grammar / typos / awkward wording (I did already catch "party of a
query" :)
- Checks for technical accuracy
- Glaring feature omissions
- Features that should be downplayed
- User testimonials / quotes
Thanks!
Jonathan
[1] https://www.postgresql.org/docs/12/release-12.html
[2] https://www.postgresql.org/about/news/1943/
Attachment | Content-Type | Size |
---|---|---|
release.en.md | text/markdown | 6.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2019-08-21 21:02:10 | Re: PostgreSQL 12 Press Release - First Draft |
Previous Message | Mark Wong | 2019-08-01 00:32:21 | exhibiting at DjangCon San Diego Sept 22-27, 2019 |