You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Search through the issues to see if your particular issue has already been discovered and possibly addressed
6
+
2. Open an issue if you can't find anything helpful
7
+
3. Open a PR for proposed changes
8
+
9
+
## Commit Guidelines
10
+
11
+
I have chosen to loosely follow the [Angular Commit Guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit)
12
+
13
+
# Documentation
14
+
15
+
If you'd like to help us improve our documentation, please checkout our [GitHub pages repository](https://github.com/json-api-dotnet/json-api-dotnet.github.io) where we host our documentation.
16
+
17
+
# Backporting Features To Prior Releases
18
+
19
+
To backport a feature that has been approved and merged into `master`:
20
+
21
+
## Requester
22
+
23
+
Open an issue requesting the feature you would like backported. The change will be reviewed based on:
24
+
25
+
- compatibility
26
+
- difficulty in porting the change
27
+
- the added value the feature provides for users on the older versions
28
+
- how difficult it is for users to migrate from the older version to the newer version
29
+
30
+
## Maintainer
31
+
32
+
- Checkout the version you want to apply the feature on top of and create a new branch to release the new version:
33
+
```
34
+
git checkout tags/v2.5.1 -b release/2.5.2
35
+
```
36
+
- Cherrypick the merge commit: `git cherry-pick {git commit SHA}`
37
+
- Bump the package version in the csproj
38
+
- Make any other compatibility, documentation or tooling related changes
39
+
- Push the branch to origin and verify the build
40
+
- Once the build is verified, create a GitHub release, tagging the release branch
41
+
- Open a PR back to master with any other additions
0 commit comments