move EOL up

Author: pdurbin

doc/release-notes/6.9-release-notes.md

@@ -124,6 +124,16 @@ Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/late
 - For `/api/admin/dataverse/{dataverse-alias}/storageDriver` and `/api/datasets/{identifier}/storageDriver` the driver name is no longer returned in data.message. Instead, it is returned as data.name (along with other information about the storageDriver). See [the guides](https://guides.dataverse.org/en/6.9/api/native-api.html#configure-a-dataset-to-store-all-new-files-in-a-specific-file-store), #11695, and #11664.
 - The POST /api/admin/makeDataCount/{id}/updateCitationsForDataset processing is now asynchronous and the response no longer includes the number of citations. The response can be OK if the request is queued or 503 if the queue is full (default queue size is 1000). See #11777 and #11781.
 
+## End-Of-Life (EOL) Announcements
+
+### PostgreSQL 13 Reached EOL on 13 November 2025
+
+We mentioned this in the Dataverse [6.6](https://github.com/IQSS/dataverse/releases/tag/v6.6) and [6.8](https://github.com/IQSS/dataverse/releases/tag/v6.8) release notes, but as a reminder, according to https://www.postgresql.org/support/versioning/ PostgreSQL 13 reached EOL on 13 November 2025. As mentioned in the [Installation Guide](https://guides.dataverse.org/en/6.9/installation/prerequisites.html#postgresql), we recommend running PostgreSQL 16 since it is the version we test with in our continuous integration ([since](https://github.com/gdcc/dataverse-ansible/commit/8ebbd84ad2cf3903b8f995f0d34578250f4223ff) February 2025). The [Dataverse 5.4 release notes](https://github.com/IQSS/dataverse/releases/tag/v5.4) explained the upgrade process from 9 to 13 (e.g. pg_dumpall, etc.) and the steps will be similar. If you have any problems, please feel free to reach out (see "getting help" in these release notes).
+
+### Payara 6 Reaching EOL with 6.2025.11
+
+As explained in #12020 and https://payara.fish/blog/payara-6-community-end-of-life/ Payara 6.2025.11 is the last release in the 6.x series. A pull request at #12043 to upgrade to Payara 7 has already been made but won't make it into this release of Dataverse. You are welcome to try it out and give feedback.
+
 ## Developer Updates
 
 - The ExportDataProvider framework in the dataverse-spi package has been extended, adding some extra options for developers of metadata exporter plugins. See [the guides](https://guides.dataverse.org/en/6.9/developers/metadataexport.html#building-an-exporter) #11766, and #11767.
@@ -160,16 +170,6 @@ Note: Despite the validation of setting names and languages, the content of any
 
 See also #11639 and #11654.
 
-## End-Of-Life (EOL) Announcements
-
-### PostgreSQL 13 Reached EOL on 13 November 2025
-
-We mentioned this in the Dataverse [6.6](https://github.com/IQSS/dataverse/releases/tag/v6.6) and [6.8](https://github.com/IQSS/dataverse/releases/tag/v6.8) release notes, but as a reminder, according to https://www.postgresql.org/support/versioning/ PostgreSQL 13 reached EOL on 13 November 2025. As mentioned in the [Installation Guide](https://guides.dataverse.org/en/6.9/installation/prerequisites.html#postgresql), we recommend running PostgreSQL 16 since it is the version we test with in our continuous integration ([since](https://github.com/gdcc/dataverse-ansible/commit/8ebbd84ad2cf3903b8f995f0d34578250f4223ff) February 2025). The [Dataverse 5.4 release notes](https://github.com/IQSS/dataverse/releases/tag/v5.4) explained the upgrade process from 9 to 13 (e.g. pg_dumpall, etc.) and the steps will be similar. If you have any problems, please feel free to reach out (see "getting help" in these release notes).
-
-### Payara 6 Reaching EOL with 6.2025.11
-
-As explained in #12020 and https://payara.fish/blog/payara-6-community-end-of-life/ Payara 6.2025.11 is the last release in the 6.x series. A pull request at #12043 to upgrade to Payara 7 has already been made but won't make it into this release of Dataverse. You are welcome to try it out and give feedback.
-
 ## New Settings
 
 ### New JVM Options (MicroProfile Config Settings)