Design & Implement a script that will automatically generate a release branch #240

New issue

Open

opened 2025-11-27 10:54:35 -06:00 by minosgalanakis · 0 comments

minosgalanakis commented

2025-11-27 10:54:35 -06:00

(Migrated from github.com)

Suggested enhancement

This task contains the requirement to build a script that will automatically generate release branches. The script should aimed to be executed in the restricted repositories and be capable of:

Fetch public branches and capture the hashes of the input
Merging -restricted branches onto public ones
Determine the name convention of the release branches based as described in therelease process
If the merge is clean it shoud return 0 and the name of the branch that contains the RC. If a merge conflict happens, it should abort the merge and return -1

Optional and good to have features that may be moved to a future issue:

Cherry pick specific commits on top of the result after the merge.
Create input sync braches, as described in the release process by moving the submodule pointers for all release inputs.

Mbed TLS needs this because it facilitates release creation and streamlines reviews. It will also enable the nighly CI to test and notify us in case the codebase is broken, ahead of starting a release.

# Suggested enhancement This task contains the requirement to build a script that will automatically generate release branches. The script should aimed to be executed in the restricted repositories and be capable of: - Fetch public branches and capture the hashes of the input - Merging -restricted branches onto public ones - Determine the name convention of the release branches based as described in the[release process](https://confluence.arm.com/pages/viewpage.action?pageId=2174475414) - If the merge is clean it shoud return 0 and the name of the branch that contains the RC. If a merge conflict happens, it should abort the merge and return -1 Optional and good to have features that may be moved to a future issue: - Cherry pick specific commits on top of the result after the merge. - Create input sync braches, as described in the [release process](https://confluence.arm.com/pages/viewpage.action?pageId=2174475414) by moving the submodule pointers for all release inputs. Mbed TLS needs this because it facilitates release creation and streamlines reviews. It will also enable the nighly CI to test and notify us in case the codebase is broken, ahead of starting a release.

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#240

No description provided.

Rows
Columns