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
* For beta releases, use a version like ``(2, 1, '0b1')``
9
-
* For release candidates, use a version like ``(2, 1, '0rc1')``
10
-
* When in doubt, follow PEP 440 versioning
11
-
* Add the new version in ``docs.yaml``
12
-
* Commit the changelog and version changes, e.g. ``git commit -m'version 1.0.0'``
13
-
* Tag the release. For example: ``git tag -a 1.0.0 -m 'version 1.0.0'``
14
-
* Push the tag and new ``master``: ``git push origin 1.0.0 ; git push origin master``
15
-
* Update the `python-driver` submodule of `python-driver-wheels`,
16
-
commit then push. This will trigger TravisCI and the wheels building.
17
-
* For a GA release, upload the package to pypi::
18
-
19
-
# Clean the working directory
20
-
python setup.py clean
21
-
rm dist/*
22
-
23
-
# Build the source distribution
24
-
python setup.py sdist
25
-
26
-
# Download all wheels from the jfrog repository and copy them in
27
-
# the dist/ directory
28
-
cp /path/to/wheels/*.whl dist/
29
-
30
-
# Upload all files
31
-
twine upload dist/*
32
-
33
-
* On pypi, make the latest GA the only visible version
34
-
* Update the docs (see below)
35
-
* Append a 'postN' string to the version tuple in ``cassandra/__init__.py``
36
-
so that it looks like ``(x, y, z, 'postN')``
37
-
38
-
* After a beta or rc release, this should look like ``(2, 1, '0b1', 'post0')``
39
-
40
-
* After the release has been tagged, add a section to docs.yaml with the new tag ref::
41
-
42
-
versions:
43
-
- name: <version name>
44
-
ref: <release tag>
45
-
46
-
* Commit and push
47
-
* Update 'cassandra-test' branch to reflect new release
48
-
49
-
* this is typically a matter of merging or rebasing onto master
50
-
* test and push updated branch to origin
51
-
52
-
* Update the JIRA versions: https://datastax-oss.atlassian.net/plugins/servlet/project-config/PYTHON/versions
53
-
54
-
* add release dates and set version as "released"
55
-
56
-
* Make an announcement on the mailing list
5
+
* Add the new version in ``docs/conf.py`` (variables: ``TAGS``, ``LATEST_VERSION``, ``DEPRECATED_VERSIONS``).
6
+
* For patch version releases (like ``3.26.8-scylla -> 3.26.9-scylla``) replace the old version with new one in ``TAGS`` and update ``LATEST_VERSION``.
7
+
* For minor version releases (like ``3.26.9-scylla -> 3.27.0-scylla``) add new version to ``TAGS``, update ``LATEST_VERSION`` and add previous minor version to ``DEPRECATED_VERSIONS``.
8
+
* Commit the version changes, e.g. ``git commit -m 'Release 3.26.9'``
9
+
* Tag the release. For example: ``git tag -a 3.26.9-scylla -m 'Release 3.26.9'``
10
+
* Push the tag and new ``master`` SIMULTANEOUSLY: ``git push --atomic origin master v6.0.21-scylla``
11
+
* Now new version and its docs should be automatically published. Check `PyPI <https://pypi.org/project/scylla-driver/#history>`_ and `docs <https://python-driver.docs.scylladb.com/stable/>`_ to make sure its there.
12
+
* If you didn't push branch and tag simultaneously (or doc publishing failed for other reason) then restart the relevant job from GitHub Actions UI.
13
+
* Publish a GitHub Release and a post on community forum.
57
14
58
15
Building the Docs
59
16
=================
@@ -62,7 +19,10 @@ To build and preview the documentation for the ScyllaDB Python driver locally, y
62
19
This is necessary for autogenerating the reference documentation of the driver.
63
20
You can find detailed instructions on how to install the driver in the `Installation guide <https://python-driver.docs.scylladb.com/stable/installation.html#manual-installation>`_.
64
21
65
-
After installing the driver, you can build and preview the documentation by following the steps outlined in the `Quickstart guide <https://sphinx-theme.scylladb.com/stable/getting-started/quickstart.html>`_.
22
+
After installing the driver, you can build the documentation:
23
+
- Make sure you have Python version compatible with docs. You can see supported version in ``docs/pyproject.toml`` - look for ``python`` in ``tool.poetry.dependencies`` section.
24
+
- Install poetry: ``pip install poetry``
25
+
- To preview docs in your browser: ``make -C docs preview``
66
26
67
27
Tests
68
28
=====
@@ -81,26 +41,22 @@ You can run a specific test method like so::
81
41
82
42
Running Integration Tests
83
43
-------------------------
84
-
In order to run integration tests, you must specify a version to run using the ``CASSANDRA_VERSION`` or ``DSE_VERSION`` environment variable::
The test will start the appropriate Cassandra clusters when necessary but if you don't want this to happen because a Cassandra cluster is already running the flag ``USE_CASS_EXTERNAL`` can be used, for example::
0 commit comments