8000 Branching requirements for feature bands · Issue #2707 · dotnet/dotnet · GitHub
[go: up one dir, main page]

Skip to content

Branching requirements for feature bands #2707

@mthalman

Description

@mthalman

With the support of feature bands in the VMR, there are specific steps to take when branching to ensure the feature band branch is configured correctly.

The 2xx feature band (release/X.0.2xx branch) of every major .NET version requires the following steps after its branch is first created:

  • Remove all "shared component" repos from the src directory. The list of repos are defined by the SharedRepositoryReference item group (example from 10.0).
  • Update branding from 1xx to 2xx (example from 10.0).
  • Add a root-level dependency on Microsoft.NET.Sdk. This references the SDK version produced from the 1xx branch that 2xx will be dependent on (example from 10.0).
  • Setup darc subscriptions for Microsoft.NET.Sdk and all dependencies of sub-repos to reference the output of the VMR from the 1xx branch.
  • Set excludeRuntimeDependentJobs parameter to true in all eng/piplines/*.yml files. Related: 30c76e5

Subsequent feature band branches (3xx, 4xx) do not require additional source changes as these are already branched from 2xx which has these changes applied. But darc subscriptions will still need to be configured.

These steps should be automated in a branching/branding script.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0