microsoft / microsoft/api-guidelines
Difference between branches master and vNext
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 23.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
The default branch on GitHub is currently set to vNext if I'm not mistaken.
Is there a difference between master and vNext? Is master obsolete, vNext a work-in-progress and still to be validated, ...?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the current status and contents of the master and vNext branches, then review the repository's existing guidance for branch usage. Done means the relationship between the branches, their validation status, and which should be treated as current is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100