-
-
Notifications
You must be signed in to change notification settings - Fork 121
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
051c734
commit a8fd591
Showing
2 changed files
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# Contributing | ||
|
||
All contributors are welcome. Please use issues and pull requests to contribute to the project. And update [CHANGELOG.md](CHANGELOG.md) when committing. | ||
|
||
# Release Process | ||
|
||
1. Confirm the build is passing in travis | ||
1. This automatically checks the pod file is building | ||
2. Create a release commit, see [prior releases](https://github.com/fulldecent/FDTake/releases) for an example | ||
1. Update the change log to label the latest improvements under the new version name | ||
2. Update the podspec version number | ||
3. Tag the release in GitHub | ||
1. Create the release commit | ||
2. Create the release with notes from the change log | ||
3. Push the podspec to cocoapods | ||
1. `pod trunk push` | ||
4. Create Carthage binaries | ||
1. `carthage build --no-skip-current` | ||
2. `carthage archive FDBarGuage` | ||
3. Add to the GitHub release |