[tor-commits] [sbws/master] new: docs: Include script on how to release
juga at torproject.org
juga at torproject.org
Tue Aug 11 13:52:52 UTC 2020
commit 6d39f0f2b7149d3453c33ff2c5fa0ec5fe6fa239
Author: juga0 <juga at riseup.net>
Date: Wed Feb 6 19:05:21 2019 +0000
new: docs: Include script on how to release
---
docs/source/contributing.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/docs/source/contributing.rst b/docs/source/contributing.rst
index 15da287..3cb4bc1 100644
--- a/docs/source/contributing.rst
+++ b/docs/source/contributing.rst
@@ -136,6 +136,9 @@ Commits
Each commit should reference the Tor Project Trac ticket (example: ``#12345``)
and possibly the bugfix version.
+From version 1.0.3, the commit title should start by ``new`` or ``fix`` or
+``change``. The commit message should contain ``Closes: #bugnumber``.
+
Try to make each commit a logically separate changes.::
As a general rule, your messages should start with a single line thatâs
@@ -258,6 +261,7 @@ Create a ./CHANGELOG.rst file.
Each entry should reference the Tor Project Trac ticket (example: ``#12345``)
and possibly the bugfix version.
Until version 1.0.2 we have followed `keep a changelog`_ format.
+From version 1.0.3, run ``./scripts/maint/release.py`` to create new releases.
.. _commit-msg:
More information about the tor-commits
mailing list