commit 64d1ba7a89b479f77ac83073e0f3f834a6fec63c
parent 93be11c8cd5f40438af121a4ac23ce19b097e3f9
Author: Christian Grothoff <christian@grothoff.org>
Date: Sun, 22 Mar 2026 10:50:22 +0100
expand release process explanation
Diffstat:
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git a/developers/style.rst b/developers/style.rst
@@ -28,7 +28,7 @@ Only one variable should be declared per line:
// bad
int i,j;
-
+
// good
int i;
int j;
@@ -304,7 +304,7 @@ The convention is to define a macro on a per-file basis to manage logging:
#define LOG(kind,...)
[logging_macro] (kind, "[component_name]", __VA_ARGS__)
-The table below indicates the substitutions which should be made
+The table below indicates the substitutions which should be made
for ``[component_name]`` and ``[logging_macro]``.
======================== ========================================= ===================
@@ -331,7 +331,7 @@ symbols defined in ``gnunet_common.h``.
Private symbols, including ``struct``\ s and macros, must not be prefixed.
In addition, they must not be exported in a way that linkers could use them
or other libraries might see them via headers. This means that they must
-**never** be declared in ``src/include``, and only declared or defined in
+**never** be declared in ``src/include``, and only declared or defined in
C source files or headers under ``src/[module_name]``.
@@ -365,7 +365,7 @@ For writing portable shell scripts, these tools are useful:
* https://wiki.ubuntu.com/DashAsBinSh, and
* https://mywiki.wooledge.org/Bashism
-Test cases and performance tests should follow the naming conventions
+Test cases and performance tests should follow the naming conventions
``test_[module-under-test]_[test_description].c`` and
``perf_[module-under-test]_[test_description].c``, respectively.
@@ -503,15 +503,17 @@ In this order do:
3. *Optional*: Update bootstrap HELLO file and update GANA generated files using ``./scripts/gana_update.sh``
-4. Update NEWS file and PO files and commit
+4. Update NEWS file, debian/changelog (adding an entry for the new version), update the PO files and commit
5. Tag the release (Named commit!)
6. Create and test tarballs
-7. Upload tarball
+7. Build and publish Debian and Ubuntu packages using taler-deployment.git/packaging/ng/ (see README there)
+
+8. Upload tarball
-8. Write release announcement
+9. Write release announcement
**(1)** Make sure the ``contrib/handbook`` submodule
@@ -608,19 +610,19 @@ For minor releases, we only write a brief statement:
This is a bugfix release for gnunet 0.21.1. It primarily addresses some
connectivity issues introduced with our new transport subsystem.
-
+
Links
-
+
Source: https://ftpmirror.gnu.org/gnunet/gnunet-0.21.2.tar.gz (https://ftpmirror.gnu.org/gnunet/gnunet-0.21.2.tar.gz.sig)
Detailed list of changes: https://git.gnunet.org/gnunet.git/log/?h=v0.21.2
NEWS: https://git.gnunet.org/gnunet.git/tree/NEWS?h=v0.21.2
The list of closed issues in the bug tracker: https://bugs.gnunet.org/changelog_page.php?version_id=440
-
+
The GPG key used to sign is: 3D11063C10F98D14BD24D1470B0998EF86F59B6A
-
+
Note that due to mirror synchronization, not all links may be
functional early after the release. For direct access try
- https://ftp.gnu.org/gnu/gnunet/
+ https://ftp.gnu.org/gnu/gnunet/
The announcement is posted to ``gnunet-developers@gnu.org`` as well as
``help-gnunet@gnu.org``.
