content/post/release-of-1.17.0.md

@@ -27,7 +27,7 @@ Read on to learn about major new features and breaking changes.
 
 ### :rocket: Package Registry ([#16510](https://github.com/go-gitea/gitea/pull/16510))
 
-Thanks to [@KN4CK3R](https://github.com/KN4CK3R), Gitea now includes a package registry for various package managers (Composer, Conan, Helm, Maven, npm, NuGet, OCI Container images, PypI, PyPI, Ruby Gems).
+Thanks to [@KN4CK3R](https://github.com/KN4CK3R), Gitea now includes a package registry for various package managers (Composer, Conan, Generic, Helm, Maven, npm, NuGet, OCI Containers (Docker), PyPI and RubyGems).
 This will be very useful for teams that want to deploy their software from their own infrastructure.
 
 To start using it, head over to the extensive [documentation for this feature](https://docs.gitea.io/en-us/packages/overview/).
@@ -74,27 +74,41 @@ Note that this feature will only be enabled when the target branch has branch pr
 |-|-|
 | ![screenshot 1](/demos/19648/1.png) | ![screenshot 2](/demos/19648/2.png) |
 
-### :rocket: Allow edits by maintainers ([#18002](https://github.com/go-gitea/gitea/pull/18002))
+### Allow edits by maintainers ([#18002](https://github.com/go-gitea/gitea/pull/18002))
 
 Thanks to [@qwerty287](https://github.com/qwerty287), Gitea now allows you to decide if maintainers of the upstream 
 repository can push to the head branch of your PR when creating a Pull Request from a fork.
 This enables a workflow similar to how Gitea itself is maintained currently and can simplify the PR workflow for open source development.
 
-### :rocket: Permanent issue (and PR) deletion ([#19032](https://github.com/go-gitea/gitea/pull/19032))
+### Permanent issue (and PR) deletion ([#19032](https://github.com/go-gitea/gitea/pull/19032))
 
 Thanks to [@fnetX](https://codeberg.org/fnetX), to combat spam and confidential information, issues (and subsequently PRs) can now be permanently deleted.  
 A repository admin or instance admin can find the delete button at the bottom of the sidebar of the issue or pull reuqest.
 
-### :rocket: Generate table of contents in wikis ([#19873](https://github.com/go-gitea/gitea/pull/19873))
+### Generate table of contents in wikis ([#19873](https://github.com/go-gitea/gitea/pull/19873))
 
 Thanks to [@zeripath](https://github.com/zeripath), wiki pages now show their logical structure automatically in the sidebar. This removes the need to manually maintain a ToC and helps you to skim for the most important sections.
 
-### :rocket: Customizing the default commit messages ([#18177](https://github.com/go-gitea/gitea/pull/18177))
+### Customizing the default commit messages ([#18177](https://github.com/go-gitea/gitea/pull/18177))
 
 Thanks to [@lunny](https://github.com/lunny), you can now set the default merge message used for merging PRs.  
 The customization files must be in `.gitea/default_merge_message/<uppercase_merge_style>_TEMPLATE.md`.  
 More information on the file names and possible variables can be found [here](https://docs.gitea.io/en-us/issue-pull-request-templates/).
 
+### Keeping the original ID of issues ([#18446](https://github.com/go-gitea/gitea/pull/18446))
+
+When you migrate a repository including its issues, their original ID will be persisted.
+This is only the first step to allow complete mirroring of issues and Pull Requests from other (Gitea, GitHub, GitLab, ...) instances, with more to come in later releases.
+
+### Federation Progress ([#19561](https://github.com/go-gitea/gitea/pull/19561) & [#19462](https://github.com/go-gitea/gitea/pull/19462))
+
+Gitea 1.17 lays the foundation to allow instances to communicate with each other in the future:  
+A new API path to allow basic communication of statistics between each other was added ([#19561](https://github.com/go-gitea/gitea/pull/19561)).  
+Additionally, with [#19462](https://github.com/go-gitea/gitea/pull/19462), basic global data about users such as the preferred avatar can now be communicated.  
+
+Federation is under active development, and it will be interesting to see what will be achieved in the next few releases.  
+Stay tuned for what is yet to come!
+
 ---
 
 ## Breaking Changes
@@ -112,11 +126,11 @@ Emails must only contain characters in ``a-zA-Z0-9.!#$%&'*+-/=?^_{|}`~``. Additi
 
 ### :exclamation: Renamed configuration options for ACME / Let's Encrypt ([#18340](https://github.com/go-gitea/gitea/pull/18340))
 
-Configuration settings have been renamed from `LETSENCRYPT` to `ACME`:
+Configuration settings have been renamed from `LETSENCRYPT` to `ACME`. The old settings are deprecated and will be removed in 1.18, you should migrate now.
 
 - `ENABLE_LETSENCRYPT` → `ENABLE_ACME`
 - `LETSENCRYPT_URL` → `ACME_URL`
-- `LETSENCRYPT_ACCEPT_TOS` → `ACME_ACCEPT_TOS`
+- `LETSENCRYPT_ACCEPTTOS` → `ACME_ACCEPTTOS`
 - `LETSENCRYPT_DIRECTORY` → `ACME_DIRECTORY`
 - `LETSENCRYPT_EMAIL` → `ACME_EMAIL`