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: RELEASE.md
+30-6Lines changed: 30 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -16,19 +16,43 @@ The SDK follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html) and t
16
16
17
17
1. Create a new GitHub release:
18
18
* From the GitHub UI:
19
-
* Navigate to the releases UI
20
-
* Set tag to release version
21
-
* Set target to `main`
19
+
* Navigate to the [releases UI](https://github.com/planetlabs/planet-client-python/releases), and select "Draft a new release".
20
+
* Choose or create a tag for the release version. The is expected to simply be the [PEP 440](https://peps.python.org/pep-0440/)
21
+
compliant semantic version number, without any prefix or other adornments. Examples, from most to least mature:
22
+
* Production release: `2.3.4`
23
+
* Release candidate: `2.3.4rc1`
24
+
* Beta release: `2.3.4b1`
25
+
* Alpha release: `2.3.4a1`
26
+
* Alpha development pre-release build: `2.3.4a1.dev1`
27
+
* Set target the release branch. This should normally be `main` for production releases.
22
28
* Set title to tag release version
23
29
* Describe the change(s) that are shipping with this version in the release description
24
30
* Alternatively, create a release from the GitHub CLI:
25
31
* Make sure the pre-requisite [gh](https://cli.github.com/manual/gh) CLI is installed, and optionally review the docs for CLI command [gh release create](https://cli.github.com/manual/gh_release_create)
26
32
* By default, `gh release create` will automatically tag releases from the latest state of the default branch
27
33
* Run CLI command `gh release create {VERSION} --notes "{RELEASE NOTES}"` where `VERSION` is the release version and `RELEASE NOTES` is the description of changes
28
-
2. Verify the successful run of the Github Action `Autopublish to TestPyPI` and validate the test release on [test.pypi.org](https://test.pypi.org/project/planet/)
29
-
3. Run the Github Action `Publish on PyPI`
34
+
2. Verify the successful run of the Github Action [`Autopublish to TestPyPI`](https://github.com/planetlabs/planet-client-python/actions/workflows/autopublish-testpypi.yml) and validate the test release on [test.pypi.org](https://test.pypi.org/project/planet/)
35
+
3. Run the Github Action [`Publish on PyPI`](https://github.com/planetlabs/planet-client-python/actions/workflows/publish-pypi.yml)
30
36
4. Verify the successful run of the Github Action `Publish on PyPI` and validate the release on [pypi.org](https://pypi.org/project/planet/)
31
-
5. Verify the successful publishing of documentation to [Read the Docs](https://planet-sdk-for-python-v2.readthedocs.io/en/latest/)
37
+
5. Verify the successful and correct publishing of documentation to Read the Docs.
38
+
Read the Docs publishing should be triggered automatically by Github
* Published to [planet-sdk-for-python](https://planet-sdk-for-python.readthedocs.io/en/latest/) (Note the new version-less project slug in DNS name).
46
+
*_`default`_: [https://planet-sdk-for-python.readthedocs.io/](https://planet-sdk-for-python.readthedocs.io/) - Should point to same version as `stable`.
47
+
*`stable`: [https://planet-sdk-for-python.readthedocs.io/en/stable/](https://planet-sdk-for-python.readthedocs.io/en/stable/) - Should point to the highest stable release version.
48
+
*`latest`: [https://planet-sdk-for-python.readthedocs.io/en/latest/](https://planet-sdk-for-python.readthedocs.io/en/latest/) - Should point to the most recent build from `main`.
49
+
*_`version`_: [https://planet-sdk-for-python.readthedocs.io/en/X.YY.ZZ/](https://planet-sdk-for-python.readthedocs.io/en/X.YY.Z/) - Should point to version `X.YY.ZZ`.
50
+
* Published to [planet-sdk-for-python-v2](https://planet-sdk-for-python-v2.readthedocs.io/en/latest/) (Note the older "v2" in the project slug in the DNS name).
51
+
*_`default`_: [https://planet-sdk-for-python-v2.readthedocs.io/](https://planet-sdk-for-python-v2.readthedocs.io/) - Should point to same version as `stable`.
52
+
*`stable`: [https://planet-sdk-for-python-v2.readthedocs.io/en/stable/](https://planet-sdk-for-python-v2.readthedocs.io/en/stable/) - Should point to the highest stable release version.
53
+
*`latest`: [https://planet-sdk-for-python-v2.readthedocs.io/en/latest/](https://planet-sdk-for-python-v2.readthedocs.io/en/latest/) - Should point to the most recent build from `main`.
54
+
*_`version`_: [https://planet-sdk-for-python-v2.readthedocs.io/en/X.YY.ZZ/](https://planet-sdk-for-python-v2.readthedocs.io/en/X.YY.ZZ/) - Should point to version `X.YY.ZZ`.
55
+
* Pre-release versions should _not_ impact the default version of the documentation. Pre-release version may be published as the `latest` version.
Copy file name to clipboardExpand all lines: design-docs/content-plan.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Content Plan Planet SDK (v2)
2
2
3
-
This document is a response to the issue #353: Quantify 'accurate and complete documentation' required for initial release. After a review of existing content, the following recommendations have been accepted as part of the V2 release. Documentation tickets will be derived from the recommendations, below.
3
+
This document is a response to the [issue #353](https://github.com/planetlabs/planet-client-python/issues/353): Quantify 'accurate and complete documentation' required for initial release. After a review of existing content, the following recommendations have been accepted as part of the V2 release. Documentation tickets will be derived from the recommendations, below.
4
4
5
5
## Overview
6
6
@@ -19,7 +19,7 @@ The SDK and CLI are low-level interfaces mirroring much of the API, itself. Whil
19
19
20
20
We are currently publishing documentation on [planet.com](https://docs.planet.com/develop/sdks/#planet-sdk-for-python-and-cli), [github.com](https://github.com/planetlabs/planet-client-python), and on [readthedocs.com](https://planet-sdk-for-python-v2.readthedocs.io). Providing a single source of truth (SSoT) ensures one definitive source of documentation, reducing the dilution of information, errors, and maintenance efforts.
21
21
22
-
### Ticket to be filed
22
+
### Tickets to be filed
23
23
24
24
Implement mkdocs to leverage features of readthedocs.com, but publish only on one platform. This would be planet.com unless we are making a concerted effort to recruit 3rd party contributors to the SDK, in which case, it could stay on readthedocs.com. So the publication landscape would be as follows:
Pursuant to the [Content Plan](./content-plan.md) developed as part of the
5
+
v2.0 release of the SDK, [_ReadTheDocs.io_](https://planet-sdk-for-python.readthedocs.io/)
6
+
is used to host the single source of truth for SDK documentation. SDK documentation
7
+
is largely confined to the specifics of using the SDK. More general Planet Platform
8
+
narrative and HTTP API documentation should be hosted on the Planet documentation site
9
+
at [docs.planet.com](https://docs.planet.com/).
10
+
11
+
## Version Management
12
+
_ReadTheDocs.io_ hosts multiple versions of the documentation simultaneously.
13
+
All versions of the documentation will be published under a _ReadTheDocs.io_
14
+
URL that explicitly includes the SDK version so that PyPi published packages
15
+
will always have corresponding _ReadTheDocs.io_ documentation for users.
16
+
17
+
Additionally, the following symbolic names are maintained:
18
+
*[**default**](https://planet-sdk-for-python.readthedocs.io/) - Should point to same version as `stable`.
19
+
*[**stable**](https://planet-sdk-for-python.readthedocs.io/en/stable/) - Should point to the highest stable release version.
20
+
*[**latest**](https://planet-sdk-for-python.readthedocs.io/en/latest/) - Should point to the most recent build from the current mainline major version branch.
21
+
22
+
Version management is handled by _ReadTheDocs.io_[automation rules](https://app.readthedocs.org/dashboard/planet-sdk-for-python/rules/).
23
+
24
+
## _ReadTheDocs.io_ Planet PBC Account
25
+
Planet currently publishes to _ReadTheDocs.io_ as a [community](https://about.readthedocs.com/pricing/#/community)
26
+
project. It is understood that this means that ads may be displayed on hosted documentation. (Ref: cleared
27
+
with Planet Engineering Management in April 2025.)
0 commit comments