Azure / Azure/Azurite

[Announcement] Azurite branching strategy change

Open
#475 1 comment 0 reactions 0 assignees View on GitHub
announcement stale
Dominant language
TypeScript
Stars
2.3k
Forks
393
Avg merge
1d 20h
Merged PRs (30d)
36

Description

Previously, Azurite V3 repo has 2 branches. Master branch is release branch which is always align with latest published released package. Dev branch accepts daily development commits. We are considering dropping dev branch and only keep master branch as develpment branch:

* Latest master branch commit is same/ahead of latest public released commit
* Every release will tag release commit
* All PRs should send to master
* Only rebase & squash merge into master

Please comments if any concerns.

TODO:

- [x] update contribution.md accordingly

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.