Skip to content
Snippets Groups Projects

RELEASES.md: describe the release process [ci skip]

Merged Nikos Mavrogiannopoulos requested to merge nmav/gnutls:tmp-releases into master
1 unresolved thread

This describes the release process and is a starting point for discussion on automating it.

Checklist

  • Commits have Signed-off-by: with name/author being identical to the commit author
  • Code modified for feature
  • Test suite updated with functionality tests
  • Test suite updated with negative tests
  • Documentation updated / NEWS entry present (for non-trivial changes)
  • CI timeout is 2h or higher (see Settings/CICD/General pipelines/Timeout)

Reviewer's checklist:

  • Any issues marked for closing are addressed
  • There is a test suite reasonably covering new functionality or modifications
  • Function naming, parameters, return values, types, etc., are consistent and according to CONTRIBUTION.md
  • This feature/change has adequate documentation added
  • No obvious mistakes in the code
Edited by Dmitry Baryshkov

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • added 1 commit

    • bf38c33a - RELEASES.md: describe the release process [ci skip]

    Compare with previous version

  • Nikos Mavrogiannopoulos resolved all threads

    resolved all threads

  • Dmitry Baryshkov approved this merge request

    approved this merge request

  • Dmitry Baryshkov marked the checklist item No obvious mistakes in the code as completed

    marked the checklist item No obvious mistakes in the code as completed

  • added 1 commit

    • a470cae5 - RELEASES.md: describe the release process

    Compare with previous version

  • mentioned in commit 6e999754

  • It's a bit belated, but shouldn't it also mention how and when to update the ABI related files for a release:

    • LT_CURRENT, LT_REVISION, and LT_AGE in m4/hooks.m4
    • devel/libgnutls-$(VERSION)-x86_64.abi
    • devel/libdane-$(VERSION)-x86_64.abi
  • I missed that. The m4/hooks.m4 update is mentioned in step 2 (maybe added later?). The VERSION.abi files should not be updated during the release. If there are missing steps I notice during the next release I'll update that file.

  • Daiki Ueno
    Daiki Ueno @dueno started a thread on the diff
  • 17 17 |stable|3.6.x |bi-monthly |
    18 18 |next |- | |
    19
    20
    21 # Release process
    22
    23 0. Create a new 'milestone' for the next release and move all issues present in the
    24 current release milestone.
    25 1. Verification of release notes: ensure that release notes ([NEWS](NEWS)) exist
    26 for this release, and include all significant changes since last release.
    27 2. Update of release date in [NEWS](NEWS), and bump of version number in
    28 [configure.ac](configure.ac) as well as soname numbers in [m4/hooks.m4](m4/hooks.m4).
    29 3. make distcheck
    30 4. git tag -s $(VERSION). The 3.6.12 was including both the 3.6.12 and
    31 gnutls_3_6_12 tags, but it may make sense to only use the version from
    32 now on.
    Please register or sign in to reply
    Loading