Update BranchingStrategy.md

* fix typos
* cleanup markdown
This commit is contained in:
descodess 2021-07-25 16:59:37 +02:00 committed by GitHub
parent 6c1d319d01
commit 6c15aa7708
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -17,7 +17,7 @@ That is Three-Flow applied to NetNewsWire. It would be that simple, but we have
Today (6/12/2019) we have 2 branches, main and macOS Candidate, in the main repository which will eventually grow to be 5 branches.
There will also be a number of repository forks that NetNewWire developers will create to do bug fixes and implement new features (not shown here). Typically contributers will fork the Main branch to thier own repository. They would then create a feature/bugfix branch on their repository. Once work on thier forked branch is complete, they will submit a pull request to be merged back into the main repository main.
There will also be a number of repository forks that NetNewWire developers will create to do bug fixes and implement new features (not shown here). Typically, contributors will fork the Main branch to their own repository. They would then create a feature/bugfix branch on their repository. Once work on their forked branch is complete, they will submit a pull request to be merged back into the main repository main.
## Tagging
@ -25,7 +25,7 @@ Each release should be tagged using [Semantic Versioning](https://semver.org/).
## Packages
NetNewsWire uses Swift Packages to manage project dependencies. All the packages are under the same project umbrella as NetNewWire and there are no third party dependencies to manage. These packages are mostly stable at this point. For simplicity sake, all development on the packages will continue on their repository Main branch. These packages wont be managed as separate projects with separate releases/tags at this time.
NetNewsWire uses Swift Packages to manage project dependencies. All the packages are under the same project umbrella as NetNewWire and there are no third-party dependencies to manage. These packages are mostly stable at this point. For simplicitys sake, all development on the packages will continue on their repository Main branch. These packages wont be managed as separate projects with separate releases/tags at this time.
## Summary