This is an old revision of the document!

To do for new release

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

Update 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: git archive -o ../13to14.zip HEAD $(git diff –name-only 32771f9457f48d768747d41f7fffdcc66718465e –diff-filter=ACMRTUXB)
see https://wiki.flatpress.org/dev:git:gitdiffzip

Create new release on GitHub
Copy/Paste from older release; update all version numbers in text and links to new version
Attach previously created update package

Update download pages en+de:
https://www.flatpress.org/download
https://www.flatpress.de/download

Write release announcement entry on flatpress.org; update news box on start page

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

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