You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: package/README.md
+18-20
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ Here is a rough overview of the effective release process. See the section below
76
76
* Prepare release notes in Markdown format.
77
77
78
78
* For changes that are breaking, duplicate those changes and put the duplicate lines into a separate group called Breaking Changes. That group should go at the top of the Changelog. The original lines for the breaking changes should be marked by appending "(Breaking change)" to the line. Example:
79
-
79
+
80
80
```
81
81
Breaking Changes
82
82
================
@@ -141,7 +141,7 @@ The following points assume work in a direct clone of the repository, and not in
141
141
8. Wait for Travis CI build for the tag to pass, see https://travis-ci.org/esp8266/Arduino/builds,
142
142
143
143
144
-
9. Check that the new (draft) release has been created (no editing at this point!), see https://github.com./esp8266/Arduino/releases.
144
+
9. Check that the new (draft) release has been created (no editing at this point!), see https://github.com./esp8266/Arduino/releases.
145
145
146
146
10. Check that the boards manager package .zip file has been successfully uploaded as a release artifact.
147
147
@@ -167,41 +167,39 @@ The following points assume work in a direct clone of the repository, and not in
167
167
--------------COPY BELOW THIS LINE--------------
168
168
[Reference](https://github.com./esp8266/Arduino/tree/master/package#creating-a-release-for-maintainers) for details.
169
169
170
-
-[ ]1.Open a new issue to track activities.
170
+
-[ ]1.Make sure that no issues or PRs are assigned to the milestone to be released.
171
171
172
-
-[ ]2.Make sure that no issues or PRs are assigned to the milestone to be released.
172
+
-[ ]2.Open a new issue to track activities.
173
173
174
174
-[ ]3. Assemble release notes.
175
175
176
-
-[ ]4. Make a PR with the following, [wait for Travis CI](https://travis-ci.org/github/esp8266/Arduino/builds/), and merge.
176
+
-[ ]4. Make a PR with the following, [wait for CI](https://github.com./esp8266/Arduino/pull/8034/checks), and merge.
-[ ]7. Tag the latest commit on the master branch, then push it to esp8266/Arduino
182
+
-[ ]5. Wait until the release notes have been checked by other maintainers (can be changed afterwards anyway)
187
183
188
-
-[ ]8. Wait for Travis CI build for the tag to pass, see https://travis-ci.org/esp8266/Arduino/builds,
184
+
-[ ]6. Tag the latest commit on the master branch, then push it to esp8266/Arduino
185
+
add: `git tag -a -m "Release 3.0.0" 3.0.0; git push origin 3.0.0`
186
+
remove: `git tag -d X.Y.Z; git push --delete origin X.Y.Z`
189
187
190
-
-[ ]9. Check that the new (draft) release has been created (no editing at this point!), see https://github.com./esp8266/Arduino/releases.
188
+
-[ ]7. Wait for CI build for the tag to pass (in `Actions` menu)
191
189
192
-
-[ ]10. Check that the boards manager package .zip file has been successfully uploaded as a release artifact.
190
+
-[ ]8. Check that the new (draft) release has been created (no editing at this point!), see https://github.com./esp8266/Arduino/releases.
193
191
194
-
-[ ]11. Check that the package index downloaded from https://arduino.esp8266.com/stable/package_esp8266com_index.json contains an entry for the new version (it may not be the first one).
192
+
-[ ]9. Check that the boards manager package .zip file has been successfully uploaded as a release artifact.
195
193
196
-
-[ ]12. Return to the [Travis CI options](https://travis-ci.org/esp8266/Arduino/settings) and disable `Build pushed branches`.
194
+
-[ ]10. Check that the package index downloaded from https://arduino.esp8266.com/stable/package_esp8266com_index.json contains an entry for the new version (it may not be the first one).
197
195
198
-
-[ ]13. Navigate to [release list in Github](https://github.com./esp8266/Arduino/releases), press "Edit" button to edit release description, paste release notes, and publish it.
196
+
-[ ]11. Navigate to [release list in Github](https://github.com./esp8266/Arduino/releases), press "Edit" button to edit release description, paste release notes, and publish it.
199
197
200
-
-[ ]14. In the issue tracker, remove "staged-for-release" label for all issues which have it, and close them. Close the milestone associated with the released version (the milestone should be empty per point 2 above)
198
+
-[ ]12. In the issue tracker, remove "staged-for-release" label for all issues which have it, and close them. Close the milestone associated with the released version (the milestone should be empty per point 1 above)
201
199
202
-
-[ ]15. Check that https://arduino-esp8266.readthedocs.io/en/latest/ has a new doc build for the new tag, and that "stable" points to that build. If a new build did not trigger, log into readthedoc's home here https://readthedocs.org/ (account must have been added to project as maintainer) and trigger it manually.
200
+
-[ ]13. Check that https://arduino-esp8266.readthedocs.io/en/latest/ has a new doc build for the new tag, and that "stable" points to that build. If a new build did not trigger, log into readthedoc's home here https://readthedocs.org/ (account must have been added to project as maintainer) and trigger it manually.
203
201
204
-
-[ ]16. Create a commit to the master branch, updating:
202
+
-[ ]14. Create a commit to the master branch, updating:
205
203
206
204
* The version in platform.txt and package.json files. This should correspond to the version of the *next* milestone, plus `-dev` suffix. E.g. `3.1.0-dev`.
207
205
* In main README.md go to "Latest release" section, change version number in the readthedocs link to the version which was just released, and verify that all links work.
0 commit comments