Skip to content

Allow Branch Releases #332

@hollowaykeanho

Description

@hollowaykeanho

Description

A lot of package managers (notably go and npm) are using branch release strategy to manage different release version. Hence, we have to facilitate such development seamlessly. The release must have:

  1. latest_[tech] branch - keeps the latest release artifacts.
  2. [version]_[tech] branch - keeps a version's artifacts.

Expected Behavior

branch release is available and autonomous.

Current Behavior

branch release has to be done manually.

Associated Data Files

No response

Metadata

Metadata

Labels

Done and Pending ReleaseCompleted and staging for next release.New FeatureCase is about developing a new feature/aspect.

Type

No type

Projects

Status

v3.0.0

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions