POLICY for 'Branches' requirement

[TomHennen]

The 'Branches' requirement says "If the SCS supports multiple branches, the organization MUST indicate which branches are intended for consumption. This may be implied or explicit. ..."

How can we meet this requirement here?

Options:

1. Decide "all branches that meet Source L2 requirements are considered 'intended for consumption" under the "implicit" requirement. Other tools can decide something else if they want.
2. Let users pass the set of branches (or patterns) they consider intended for consumption and only emit L2+ if the branch the VSA is generated for matches.

Spec feedback:
As currently written this spec sounds like an "Organization" requirement but it's listed as a "Source Control System" requirement. Maybe it should be tweaked to be "If the SCS supports multiple branches, the SCS MUST indicate which branches are intended for consumption. This may be implied or explicit. ..."

[mlieberman85]

Would this be an organization or at least an individual project requirement? Different projects' branches could follow the rules for different sets of branches right?

[TomHennen]

I think the spirit of the requirement is not that the org defines "this is how it works for all our repos" but rather that the org defines "this is how this repo does it".