From: | Nemo <me(at)captnemo(dot)in> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Git tag for v15 |
Date: | 2022-10-12 15:46:44 |
Message-ID: | 2e5676ba-e579-09a5-6f3a-d68208052654@captnemo.in |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Writing this on behalf of endoflife.date, where we track postgres
releases for the endoflife.date/postgres page.
We have our automation linked to git tags published on the postgres repo
mirror on GitHub[0].
It recently picked up the REL_15_0 tag[2], and compiled it here:
https://github.com/endoflife-date/release-data/blob/main/releases/postgresql.json#L452
Since v15 doesn't seem to be announced yet - this is confusing me. It
doesn't impact us anywhere (yet), since we haven't added the v15 release
cycle to our page yet, but I'd like to check if this is an incorrect tag
or? If not, what's the correct source for us to use for automation purposes?
I went through the release process on the Wiki[1], and it mentions final
version tagging as the final irreversible step, so that added to my
confusion.
Thanks,
Nemo
(Please keep me in cc for any replies)
[0]: https://github.com/postgres/postgres
[1]: https://wiki.postgresql.org/wiki/Release_process#Final_version_tagging
[2]: https://github.com/postgres/postgres/releases/tag/REL_15_0
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2022-10-12 16:04:08 | Re: Warning about using pg_stat_reset() and pg_stat_reset_shared() |
Previous Message | Tom Lane | 2022-10-12 15:01:48 | Re: create subscription - improved warning message |