someone else to do the list of acknowledgments
I would like for someone else to prepare the list of acknowledgments in
the release notes this year.
I have been preparing the list of acknowledgments in the release notes
(example: [0]https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-ACKNOWLEDGEMENTS) since PostgreSQL 10 (launched from discussions at PGCon
2017 [1]https://wiki.postgresql.org/wiki/PgCon_2017_Developer_Meeting#Release_notes_scope.2C_and_giving_credit). I'm looking to hand this off now, so that I'm not hogging
this job forever.
[0]: https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-ACKNOWLEDGEMENTS
https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-ACKNOWLEDGEMENTS
[1]: https://wiki.postgresql.org/wiki/PgCon_2017_Developer_Meeting#Release_notes_scope.2C_and_giving_credit
https://wiki.postgresql.org/wiki/PgCon_2017_Developer_Meeting#Release_notes_scope.2C_and_giving_credit
I'm happy to train the next person and hand them my tips and scripts,
or they can of course define their own processes.
So that prospective candidates know what they are getting into, the
(my) process is approximately:
1. collect names from git logs in semi-automated way
2. sort, organize, fix, and normalize names
3. check manually against git log
4. commit
5. fix up based on public feedback
6. keep updated until release
The whole thing might take about 20 to 30 hours wall-clock time.
I have found it not useful to start this too early, since you'll get a
lot of new names during the beta period. I have lately usually
started after the August beta release. (Or you can start early and
keep it updated. Again, it's your process.)
Anyone can do this, you don't need to be a committer or developer (but
you'll need to be able to produce a well-formed documentation patch).
However, I suggest that because there is a fair amount of work to
normalize, fix, and transliterate names, it would help if you've been
around for a while and have some passing familiarity with the names of
the people around here. Also, since this list is often cited for
public credit, some care and attention to detail is needed.
So, there is some time to think about this. Please discuss here if
you're interested or have questions.
(This is presupposing that we still want to do this. If you have
other ideas for a better list or no list, this is also the time to
discuss this.)
The whole thing might take about 20 to 30 hours wall-clock time.
After this dev cycle, things with a defined end to them hold a greater
attraction than they did previously.
So, there is some time to think about this. Please discuss here if
you're interested or have questions.
I am interested.
Hi,
The whole thing might take about 20 to 30 hours wall-clock time.
After this dev cycle, things with a defined end to them hold a greater attraction than they did previously.
So, there is some time to think about this. Please discuss here if
you're interested or have questions.I am interested.
+1
--
Best regards,
Aleksander Alekseev
Hi,
The whole thing might take about 20 to 30 hours wall-clock time.
After this dev cycle, things with a defined end to them hold a greater attraction than they did previously.
So, there is some time to think about this. Please discuss here if
you're interested or have questions.I am interested.
+1
Sorry, I've just realized that my +1 can be interpreted as both voting
for Corey and as volunteering for making the list of acknowledgments.
To clarify, I meant that I'm interested too :)
--
Best regards,
Aleksander Alekseev
hi.
maybe we should start working on this?
https://www.postgresql.org/developer/roadmap
says 18 will be released in September 2025.
On Sat, Aug 16, 2025 at 11:58 PM jian he <jian.universality@gmail.com>
wrote:
hi.
maybe we should start working on this?https://www.postgresql.org/developer/roadmap
says 18 will be released in September 2025.
I am.
On Sun, Aug 17, 2025 at 12:40 PM Corey Huinker <corey.huinker@gmail.com> wrote:
On Sat, Aug 16, 2025 at 11:58 PM jian he <jian.universality@gmail.com> wrote:
hi.
maybe we should start working on this?https://www.postgresql.org/developer/roadmap
says 18 will be released in September 2025.I am.
hi.
Maybe you can share the draft patch so others can review it.
https://www.postgresql.org says:
"The planned date for the general availability of PostgreSQL 18 is
September 25, 2025."
516 contributors this cycle vs 462 last cycle.
When name accents/capitalization differed, I went with the string used in
the previous year.
Some of the names that come from bug reports and doc fixes are just first
names, and the discussion threads shed no light on the full name of the
person.
I have a git log that has been "redacted", which is to say that every name
attribution has been screened out, as well as names of known past
contributors, and various other name-looking things that aren't people (ex.
Microsoft Windows) screened out. Even with all that automation it is still
over 50k lines, so if you want to double check that, make sure you have a
comfy chair.
On Tue, Sep 9, 2025 at 12:07 PM jian he <jian.universality@gmail.com> wrote:
Show quoted text
On Sun, Aug 17, 2025 at 12:40 PM Corey Huinker <corey.huinker@gmail.com>
wrote:On Sat, Aug 16, 2025 at 11:58 PM jian he <jian.universality@gmail.com>
wrote:
hi.
maybe we should start working on this?https://www.postgresql.org/developer/roadmap
says 18 will be released in September 2025.I am.
hi.
Maybe you can share the draft patch so others can review it.https://www.postgresql.org says:
"The planned date for the general availability of PostgreSQL 18 is
September 25, 2025."
Em qua., 10 de set. de 2025 às 12:11, Corey Huinker <corey.huinker@gmail.com>
escreveu:
516 contributors this cycle vs 462 last cycle.
When name accents/capitalization differed, I went with the string used in
the previous year.Some of the names that come from bug reports and doc fixes are just first
names, and the discussion threads shed no light on the full name of the
person.I have a git log that has been "redacted", which is to say that every name
attribution has been screened out, as well as names of known past
contributors, and various other name-looking things that aren't people (ex.
Microsoft Windows) screened out. Even with all that automation it is still
over 50k lines, so if you want to double check that, make sure you have a
comfy chair.
I think that "Rainier Vilela" is a mistake and should be removed.
The correct is "Ranier Vilela"
best regards,
Ranier Vilela
On 10 Sep 2025, at 17:11, Corey Huinker <corey.huinker@gmail.com> wrote:
516 contributors this cycle vs 462 last cycle.
When name accents/capitalization differed, I went with the string used in the previous year.
Some of the names that come from bug reports and doc fixes are just first names, and the discussion threads shed no light on the full name of the person.
I have a git log that has been "redacted", which is to say that every name attribution has been screened out, as well as names of known past contributors, and various other name-looking things that aren't people (ex. Microsoft Windows) screened out. Even with all that automation it is still over 50k lines, so if you want to double check that, make sure you have a comfy chair.
A few probable, or guaranteed, duplicates:
Daniel Gustafs
Daniel Gustafsson
Kuntal Ghosh
Kuntal Gosh
Yasir
Yasir Hussain
There are a few first-names-only that need to be verified, IME they resolve to
a name already on the list.
Andrew
Dmitry
Felix
--
Daniel Gustafsson
On 2025-Sep-10, Corey Huinker wrote:
Aysén Region
This is not a contributor name but a toponymic. I think you got it from this
commit:
commit 368c3fbf9da96787d4e7cae61e11518d72f75071
Author: Tom Lane <tgl@sss.pgh.pa.us> []
AuthorDate: Wed Apr 30 11:13:49 2025 -0400
CommitDate: Wed Apr 30 11:13:49 2025 -0400
Update time zone data files to tzdata release 2025b.
DST law changes in Chile: there is a new time zone America/Coyhaique
for Chile's Aysén Region, to account for it changing to UTC-03
year-round and thus diverging from America/Santiago.
Historical corrections for Iran.
Backpatch-through: 13
Also please note that my name appears twice, once with A and once with
Á (sorts at the end). The latter is correct.
"Yasir" is the same person as "Yasir Hussain".
"Anton A. Melnikov" is probably the same as "Anton Melnikov", and "David
E. Wheeler" is likely "David Wheeler".
Per /messages/by-id/18806-d70b0c9fdf63dcbf@postgresql.org
we can credit 孟令彬 as "lingbin meng".
Per /messages/by-id/tencent_CA843A8385CB3130B9ABC1E55023FC4E4D05@qq.com
we can credit 清浅 as "Chengwen Wu".
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Hay dos momentos en la vida de un hombre en los que no debería
especular: cuando puede permitírselo y cuando no puede" (Mark Twain)
On Wed, Sep 10, 2025 at 07:57:26PM +0200, Alvaro Herrera wrote:
Per /messages/by-id/tencent_CA843A8385CB3130B9ABC1E55023FC4E4D05@qq.com
we can credit 清浅 as "Chengwen Wu".
Good catch, thanks! I didn't notice his name as this message seems to
have been cut from the original thread where the bug has been
reported.
--
Michael
On Wed, Sep 10, 2025 at 11:11 PM Corey Huinker <corey.huinker@gmail.com> wrote:
516 contributors this cycle vs 462 last cycle.
When name accents/capitalization differed, I went with the string used in the previous year.
Some of the names that come from bug reports and doc fixes are just first names, and the discussion threads shed no light on the full name of the person.
I have a git log that has been "redacted", which is to say that every name attribution has been screened out, as well as names of known past contributors, and various other name-looking things that aren't people (ex. Microsoft Windows) screened out. Even with all that automation it is still over 50k lines, so if you want to double check that, make sure you have a comfy chair.
Andrei Lepikhov
Andrey Lepikhov
refers to the same person, I think.
Masao Fujii
Fujii Masao
refers to the same person too?
Junwang Zhao
Zhao Junwang
refers to the same person too?
"Hacking Discord" wrong?
hi.
Nikita
Nikita Kalinin
Nikita Malakhov
The first "Nikita" refers to the commit below
058b5152f02ef86c98a795c14dbd6a8e195f4fd1.
Author: Daniel Gustafsson <dgustafsson@postgresql.org>
Date: Thu Mar 27 22:57:34 2025 +0100
Fix guc_malloc calls for consistency and OOM checks
Author: Daniel Gustafsson <daniel@yesql.se>
Reported-by: Nikita <pm91.arapov@gmail.com>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Bug: #18845
Discussion: /messages/by-id/18845-582c6e10247377ec@postgresql.org
Backpatch-through: 16
maybe we can credit it to
Nikita <pm91.arapov@gmail.com>
Wenhui Qiu
wenhui qiu
I use ``git log --grep='Wenhui Qiu' `` can not find any result.
I think ``wenhui qiu`` is the correct one.
Zhihong Yu
Ted Yu
refers to the same person too.
Álvaro Herrera
Alvaro Herrera
refers to the same person.
Hou Zhijie
Zhijie Hou
refers to the same person.
Zharkov Roman
Roman Zharkov
refers to the same person, by comparing email address
Yuki Seino
Seino Yuki
refers to the same person, by comparing email address
hi.
Kuroda Hayato
Hayato Kuroda
refers to the same person.
Takatsuka Haruka
Haruka Takatsuka
refers to the same person.
I think that "Rainier Vilela" is a mistake and should be removed.
The correct is "Ranier Vilela"best regards,
Ranier Vilela
I trust your expertise in this matter.
Apologies, several email responses went to just individuals instead of the
group.
On Wed, Sep 10, 2025 at 10:50 PM jian he <jian.universality@gmail.com>
wrote:
hi.
Nikita
Nikita Kalinin
Nikita Malakhov
The first "Nikita" refers to the commit below
058b5152f02ef86c98a795c14dbd6a8e195f4fd1.maybe we can credit it to
Nikita <pm91.arapov@gmail.com>
The email address associated doesn't show up elsewhere, so I left it just
"Nikita".
Zhihong Yu
Ted Yu
refers to the same person too.
I'm inclined to believe you, but can you cite a link between the two?
Especially one that shows a name preference.
Hou Zhijie
Zhijie Hou
refers to the same person.
Went with Hou Zhijie based on email signature.
Yuki Seino
Seino Yuki
refers to the same person, by comparing email address
Went with Yuki Seino based on email signature.
On Thu, Sep 11, 2025 at 12:35 AM jian he <jian.universality@gmail.com>
wrote:
hi.
Kuroda Hayato
Hayato Kuroda
refers to the same person.Takatsuka Haruka
Haruka Takatsuka
refers to the same person.
Fixed.
Fixed.
More than a few acknowledgements of edits went reply instead of reply-all,
but I think they've been addressed.
Down to 505 contributors from 516 in v18.
Updated credits list and full-outer-join diff lists attached.
Corey Huinker <corey.huinker@gmail.com> writes:
On Wed, Sep 10, 2025 at 10:50 PM jian he <jian.universality@gmail.com>
wrote:Zhihong Yu
Ted Yu
refers to the same person too.
I'm inclined to believe you, but can you cite a link between the two?
Especially one that shows a name preference.
The forms that appear in my local archives are
Zhihong Yu <zyu@yugabyte.com>
Ted Yu <yuzhihong@gmail.com>
While that's not evidence that would satisfy a court of law, it's
close enough for the purpose at hand.
The yugabyte.com address doesn't seem to have been active since 2022
though; recent references to it are only in messages doing
reply-to-all. I'd go with the gmail address as being current,
and therefore with "Ted" as being the person's current preference,
barring input to the contrary.
Yuki Seino
Seino Yuki
refers to the same person, by comparing email address
Went with Yuki Seino based on email signature.
Westerners tend to have a hard time distinguishing given name
from family name in Eastern names, and the lack of consistency
about that in email signatures doesn't help :-(. Our intention
in the release notes is to write given names first, but I'm sure
we've made many mistakes of that sort. Perhaps some of our
Eastern colleagues can offer some help about which way to spell
these. (Checking past iterations of the release notes could
be helpful, too.)
regards, tom lane
