File: maintguide.rst

package info (click to toggle)
pygobject 3.55.3-3
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 6,000 kB
  • sloc: ansic: 39,431; python: 26,883; sh: 114; makefile: 81; xml: 35; cpp: 1
file content (30 lines) | stat: -rw-r--r-- 994 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
================
Maintainer Guide
================

Making a Release
----------------

#. Make sure the `meson.build` file contains the right version number
#. Update the NEWS file
#. Build new version using ``python3 -m build --sdist``
#. Commit NEWS as ``"release 3.X.Y"`` and push
#. Tag with: ``git tag -s 3.X.Y -m "release 3.X.Y"``
#. Push tag with: ``git push origin 3.X.Y``
#. In case of a stable release, upload to PyPI:
   ``twine upload dist/pygobject-3.X.Y.tar.gz``
#. Commit post-release version bump to pyproject.toml
#. In case the release happens on a stable branch copy the NEWS changes to
   the main branch


Branching
---------

Each cycle after the feature freeze, we create a stable branch so development
can continue in the main branch unaffected by the freezes.

#. Create the branch locally with: ``git checkout -b pygobject-3-2``
#. Push new branch: ``git push origin pygobject-3-2``
#. In main, update pyproject.toml to what will be the next version number
   (3.3.0)