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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ Read more about CheckMates on our [documentation page](#):
36
36
37
37
The CheckMates community is happy to provide support to users of CheckMates. Project support can be found in four places depending on the type of question:
38
38
1. For usage questions, use [Stack Overflow](#) with the `CheckMates` tag.
39
-
2. For bugs, issues, or feature requests start a [Github issue](#).
39
+
2. For bugs, issues, or feature requests start a [Github issue](https://github.com/alteryx/CheckMates/issues).
40
40
3. For discussion regarding development on the core library, use [Slack](#).
41
41
4. For everything else, the core developers can be reached by email at [email protected]
Copy file name to clipboardExpand all lines: release.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,16 +3,16 @@
3
3
## 0. Pre-Release Checklist
4
4
Before starting the release process, verify the following:
5
5
* All work required for this release has been completed and the team is ready to release.
6
-
*[All Github Actions tests are green on main](#).
6
+
*[All Github Actions tests are green on main](https://github.com/alteryx/CheckMates/actions?query=branch%3Amain).
7
7
* The [ReadtheDocs build](#) for "latest" is marked as passed. To avoid mysterious errors, best practice is to empty your browser cache when reading new versions of the docs!
8
-
* The [public documentation for the "latest" branch](#) looks correct, and the [release notes](#) includes the last change which was made on main.
8
+
* The [public documentation for the "latest" branch](#) looks correct, and the [release notes](https://github.com/alteryx/CheckMates/blob/quickstart-installation_update/docs/source/release_notes.rst) includes the last change which was made on main.
9
9
* Get agreement on the version number to use for the release.
10
10
11
11
#### Version Numbering
12
12
13
13
CheckMates uses [semantic versioning](https://semver.org/). Every release has a major, minor and patch version number, and are displayed like so: `<majorVersion>.<minorVersion>.<patchVersion>`.
14
14
15
-
If you'd like to create a development release, which won't be deployed to pypi and conda and marked as a generally-available production release, please add a "dev" prefix to the patch version, i.e. `X.X.devX`. Note this claims the patch number--if the previous release was `0.12.0`, a subsequent dev release would be `0.12.dev1`, and the following release would be `0.12.2`, *not*`0.12.1`. Development releases deploy to [test.pypi.org](#) instead of to [pypi.org](#).
15
+
If you'd like to create a development release, which won't be deployed to pypi and conda and marked as a generally-available production release, please add a "dev" prefix to the patch version, i.e. `X.X.devX`. Note this claims the patch number--if the previous release was `0.12.0`, a subsequent dev release would be `0.12.dev1`, and the following release would be `0.12.2`, *not*`0.12.1`. Development releases deploy to [test.pypi.org](https://test.pypi.org/project/checkmates/) instead of to [pypi.org](https://pypi.org/project/CheckMates/).
16
16
17
17
## 1. Freeze `main` and run perf tests
18
18
After confirming the release is ready to go in step 0, we'll freeze the `main` branch and kick off the release performance tests.
0 commit comments