You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2022/07/21 14:28:16 UTC
[airflow] 13/22: Fix markdown error in Airflow Readme (#25120)
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch v2-3-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 823e2f0d3f82e0f9c523a5e2d6d0264b8c29ca91
Author: Jarek Potiuk <ja...@polidea.com>
AuthorDate: Mon Jul 18 10:59:41 2022 +0200
Fix markdown error in Airflow Readme (#25120)
The new markdown-lint is a bit more picky about headeers in markdown
(cherry picked from commit 6e592ad7565d4f8a7371dea71ce6e74e512dec11)
---
dev/README_RELEASE_AIRFLOW.md | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/dev/README_RELEASE_AIRFLOW.md b/dev/README_RELEASE_AIRFLOW.md
index f311cf556a..287b642d69 100644
--- a/dev/README_RELEASE_AIRFLOW.md
+++ b/dev/README_RELEASE_AIRFLOW.md
@@ -25,7 +25,7 @@
- [Reviewing cherry-picked PRs and assigning labels](#reviewing-cherry-picked-prs-and-assigning-labels)
- [Prepare the Apache Airflow Package RC](#prepare-the-apache-airflow-package-rc)
- [Build RC artifacts](#build-rc-artifacts)
- - [[\Optional\] Prepare new release branches and cache](#%5Coptional%5C-prepare-new-release-branches-and-cache)
+ - [Prepare new release branches and cache - optional when first minor version is released](#prepare-new-release-branches-and-cache---optional-when-first-minor-version-is-released)
- [Prepare PyPI convenience "snapshot" packages](#prepare-pypi-convenience-snapshot-packages)
- [Prepare production Docker Image RC](#prepare-production-docker-image-rc)
- [Prepare issue for testing status of rc](#prepare-issue-for-testing-status-of-rc)
@@ -199,7 +199,9 @@ The Release Candidate artifacts we vote upon should be the exact ones we vote ag
- Check out the 'test' branch
- For major/minor version release, please follow the instructions at [Prepare new release branches and cache](#%5Coptional%5C-prepare-new-release-branches-and-cache) to create the 'test' and 'stable' branches.
+ For major/minor version release, please follow the instructions at
+ [Prepare new release branches and cache](#prepare-new-release-branches-and-cache---optional-when-first-minor-version-is-released)
+ to create the 'test' and 'stable' branches.
```shell script
git checkout v${VERSION_BRANCH}-test
@@ -314,7 +316,7 @@ The Release Candidate artifacts we vote upon should be the exact ones we vote ag
svn commit -m "Add artifacts for Airflow ${VERSION}"
```
-## [\Optional\] Prepare new release branches and cache
+## Prepare new release branches and cache - optional when first minor version is released
When you just released the `X.Y.0` version (first release of new minor version) you need to create release
branches: `vX-Y-test` and `vX-Y-stable` (for example with `2.1.0rc1` release you need to create v2-1-test and