Table of Contents

To do for new release

Code

Bump version number

in core.system.php:
define('SYSTEM_VER', '1.x');

Update Change Log

first headline in CHANGELOG.md:
# yyyy-mm-dd: [FlatPress 1.x "Release Name"](https://github.com/flatpressblog/flatpress/releases/tag/1.x)
→ link is 404 for now, release will be created later

Create update package

Create update packages from last version (and maybe the one before as well). For details, see https://wiki.flatpress.org/dev:git:gitdiffzip

Create new release on GitHub

Public relations

Update download pages en+de

Publish release announcement

Update VERSION identifier

Update flatpress.org/fp/VERSION (is called by all FlatPress instances for version info) 

STABLE|1.X|UNSTABLE|1.X RCx|NOTICE|YYYY-MM-DD: FlatPress 1.X is released! <ul><li><a href="https://www.flatpress.org/<entry>/">Release announcement</a></li></ul>

Documentation

Update the wiki

Idea: Move project to Codeberg? Thoughts: It can also make sense to use both platforms. Many projects use GitHub for main development and Codeberg for a mirror image or alternative platform. Pros and cons keep ~ the balance.

Criteria Codeberg GitHub
Philosophy Non-profit, open source, community-driven Commercial, MS ecosystem
Data protection & hosting EU/DSGVO-compliant, Germany predominantly USA
Functions & integrations Basic features (issues, wikis), Gitea ecosystem Easy entry / many tutorials, issue linking, extensive CI/CD, security tools
User base & ecosystem Small, but growing slowly? Less reach Huge community
Costs completely free of charge free of charge for us as we do not use enterprise products