-
Notifications
You must be signed in to change notification settings - Fork 3
Closed
Description
Create a new branch, starting from 24.12 release, applying our unmerged commits on top of that.
In the process we might try to squash some related commits - in that case, we should leave some notes there, or in commit message (or both).
We can use this issue as a general discussion of this process.
As for branch naming: we can always rename, we may consider dev/24.12 as we're discussing this flow elsewhere, and perhaps we will adopt some of it in the end.
Additional task, that could be done during rebase: TBD
- patches classification - inspired by: https://docs.yoctoproject.org/contributor-guide/recipe-style-guide.html#patch-upstream-status
- add
Upstream-Statustag to indicate whether the patch isPending(to be submitted upstream), orInappropriate [dasharo-specific](not planned to upstream), or something else - TBD - link to the process description in docs.dasharo
- this process is still in discussion, but we have agreed that some form of classification whether we plan to upstream certain patches, or not, would be useful
I will replace this with link to the actual documentation once in place.
tlaurion
Metadata
Metadata
Assignees
Labels
No labels