@@ -46,18 +46,11 @@ twine upload dist/*
46
46
47
47
## Post release
48
48
49
- ### New branch to create for major releases
49
+ ### Merge tags in master for pre-commit
50
50
51
- The master branch will have all the new features for the ` X.Y+1 ` version
52
-
53
- If you're doing a major release, you need to create the ` X.Y ` branch where we will
54
- cherry-pick bugs to release the ` X.Y.Z+1 ` minor versions
55
-
56
- ### Merge tags in master for minor releases
57
-
58
- Merge the tag ` X.Y.Z ` in the main branch by doing a history only merge. It's done in
59
- order to signal that this is an official release tag, and for ` pre-commit autoupdate ` to
60
- works.
51
+ If the tag you just made is not part of the main branch, merge the tag ` X.Y.Z ` in the
52
+ main branch by doing a history only merge. It's done in order to signal that this is an
53
+ official release tag, and for ` pre-commit autoupdate ` to works.
61
54
62
55
``` bash
63
56
git checkout master
@@ -74,8 +67,8 @@ issue labelled as blocker.
74
67
75
68
#### Changelog
76
69
77
- - Create a new section, with the name of the release ` X.Y.Z+1 ` on the ` X.Y ` branch.
78
- - If it's a major release, also create a new section for ` X.Y+1.0 ` on the master branch
70
+ - Create a new section, with the name of the release ` X.Y.Z+1 ` or ` X.Y+1.0 ` on the
71
+ master branch.
79
72
80
73
You need to add the estimated date when it is going to be published. If no date can be
81
74
known at that time, we should use ` Undefined ` .
@@ -87,6 +80,5 @@ at the examples from `doc/whatsnew`.
87
80
88
81
### Versions
89
82
90
- Update ` __version__ ` to ` X.Y+1.0 ` in ` pylint/__pkginfo__.py ` for ` master ` and to
91
- ` X.Y.Z+1 ` for the ` X.Y ` branch. ` dev_version ` should also be back to an integer after
92
- the tag.
83
+ Update ` __version__ ` to ` X.Y+1.0 ` or ` X.Y.Z+1 ` in ` __pkginfo__ ` . ` dev_version ` should
84
+ also be back to an integer after the tag.
0 commit comments