libgit2 / libgit2/libgit2sharp
New Development Process
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
With the release of v0.22, we want to streamline the development processes a bit and make them more like the current libgit2 "development rooles". This will help those of us who work on both just a little bit saner, and hopefully also be more in line with what other projects do. This means:
- The
masterbranch is where development happens now. It's now the default branch and where new pull requests should be targeted. - Any bugfix releases we'll branch a
maint/v0.22to handle it, based on the appropriate tagged release. - Please make sure that your pull requests update the
[CHANGELOG.md](https://github.com/libgit2/libgit2sharp/blob/master/CHANGELOG.md)at the root of the repository.
We'll deal with manually merging any existing PRs that we want to take. Thanks!
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
Review the development-process announcement and the root CHANGELOG.md, along with the master and maint/v0.22 branch guidance. Confirm whether the repository still documents these conventions and whether pull requests are expected to update CHANGELOG.md; done means the current process is clearly recorded and consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- developer-experience, release
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100