Iteration v8.2 (release plan)

[MichaIng]

Day 0: Init new development cycle

To be done until: 2022-02-06

• Create a new GitHub milestone https://github.com/MichaIng/DietPi/milestones
• Select issues for the new iteration in the new milestone
• Create a new section in the DietPi Wiki
• A new development cycle starts with a subversion increment, or major version increment when we drop support for an old Debian version or old DietPi versions. The RC version during the development cycle is "-1", to clearly identify unstable version strings.
• Init CHANGELOG.md
• Add support to DietPi-Survey_report

3rd week: Beta phase

To be done until: 2022-02-26

• Merge live patches from master and remove in dev.
• Create pull requests for all required documentation changes:

To be done at: 2022-02-26

• Launch the initial beta as .0 RC version
• Advertise on GitHub
• Advertise on DietPi Forum
• Advertise on DietPi-Banner MOTD

To be done at: 2022-02-27

• Advertise on website slider: https://dietpi.com/
• Advertise on Twitter (DietPi account)
• Advertise on Facebook (DietPi group)

To be done from: 2022-02-27 - 2021-03-03

• Address bug reports with further beta iterations, e.g. .1 and .2 RC versions

2 days before the release

To be done until: 2022-03-03

• Have a release PR open on the main repo which needs to be linked from the changelog/release notes.
• Assure that update server version and DietPi-Globals default version match.
• Have the docs release PR ready and reviewed, with release notes and required changes merged into dev already.
• Have a PR on the website ready to advertise the new release via website slide and have the docs PRs all ready and reviewed.

Release

To be done at: 2022-03-05

• Make the release
• Publish the release notes in DietPi Docs
• Link the release notes from website slider
• Mention the release notes in DietPi Forum
• Update the MOTD
• Update software list in DietPi Wiki

Release announcements

To be done at: 2022-03-06

• Publish on Twitter (DietPi account)
• Publish on several Facebook groups (e.g. DietPi group)
• Announce on Hacker News
• Forge and spread a press release
• Determine if a hotfix release is needed
• Create a new release plan