Skip to content

[Feature]: Consider a Release Branch and Dev Branch Test Strategy #1114

@makubacki

Description

@makubacki

Feature Overview

Project Mu recently moved repos with release branches to a dev branch by default. This feature request is to determine whether to build both the release and dev branches in CI.

To align with the default branch in other repos and make new changes and features more readily accessible, #1112 moved the default branches used in Mu Tiano Platforms Project Mu submodules to dev branches.

Solution Overview

Since Mu consumers may use either a dev or release branch in a platform, this feature tracks consideration of testing both in Mu Tiano Platforms. This may be challenging due to backward incompatible changes made in the dev branch and common platform code being used across both. But ways to address that can be discussed further here.

Alternatives Considered

No response

Urgency

Low

Are you going to implement the feature request?

Someone else needs to implement the feature

Do you need maintainer feedback?

Maintainer feedback requested

Anything else?

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions