Design & implement a scripted process for buidling and packing a release branch #239

New issue

Open

opened 2025-11-27 10:45:28 -06:00 by minosgalanakis · 0 comments

minosgalanakis commented

2025-11-27 10:45:28 -06:00

(Migrated from github.com)

Suggested enhancement

In order to streamline releases we need a non ambigious way to perform a set of standard actions on top of a release branch. Those actions are defined by our release process:

Assemble the changelog
Update the date to the release date on Changlog and documentation
Bump the version.
Create the autogenerated files
Pack the release in a tarball while removing the git information.

Implementation is adressed by https://github.com/Mbed-TLS/mbedtls-framework/pull/231#discussion_r2494288854

Justification

Mbed TLS needs this because it facilitates release creation and streamlines reviews.

### Suggested enhancement In order to streamline releases we need a non ambigious way to perform a set of standard actions on top of a release branch. Those actions are defined by our release process: - Assemble the changelog - Update the date to the release date on Changlog and documentation - Bump the version. - Create the autogenerated files - Pack the release in a tarball while removing the git information. Implementation is adressed by https://github.com/Mbed-TLS/mbedtls-framework/pull/231#discussion_r2494288854 ### Justification Mbed TLS needs this because it facilitates release creation and streamlines reviews.

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-Mbed-TLS/mbedtls-framework#239

No description provided.

Rows
Columns