Browse Source

Preparing a release plan.

pull/59/head
Maurice Makaay 3 years ago
parent
commit
240a4a7a64
2 changed files with 17 additions and 9 deletions
  1. +15
    -0
      doc/release_plan.md
  2. +2
    -9
      doc/test_plan.md

+ 15
- 0
doc/release_plan.md View File

@ -0,0 +1,15 @@
# Release plan
All development is done in the `dev` branch. Once the development branch is
ready for a new production release, the following steps are followed:.
- branch `Year.Month.Version-release` from `dev`.
Before release, check if the minimum version requirement for ESPHome is documented
correctly in the following files:
* doc/installation.md
* README.md
* CHANGELOG.md

doc/testplan.md → doc/test_plan.md View File

@ -1,4 +1,4 @@
# Testplan
# Test plan
This is the test plan that I follow for every release. I use it to ensure that no regression has This is the test plan that I follow for every release. I use it to ensure that no regression has
been introduced. been introduced.
@ -70,11 +70,4 @@ been introduced.
## Step 3: Release the new version ## Step 3: Release the new version
Only after performing these tests successfully, the new version can be released. Only after performing these tests successfully, the new version can be released.
Before release, check if the minimum version requirement for ESPHome is documented
correctly in the following files:
* doc/installation.md
* README.md
* CHANGELOG.md
Release steps are documented in [`releaseplan.md`](releaseplan.md).

Loading…
Cancel
Save