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
Copy file name to clipboardexpand all lines: CHANGELOG.md
+9-1
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,12 @@
2
2
3
3
This project adheres to [Semantic Versioning](http://semver.org/).
4
4
5
-
Every release, along with the migration instructions, is documented on the Github [Releases page](https://github.com/SalesLoft/open-source-template/releases).
5
+
Every release, along with the migration instructions, is documented on the Github [Releases page](https://github.com/SalesLoft/gorollout/releases).
6
+
7
+
### v1.1.0
8
+
9
+
Added support for controlling the randomizing percentage between feature flags. Setting to false will ensure that features are active for the same teams when rolled out the same percentage.
10
+
11
+
### v1.0.0
12
+
13
+
Initial release of library. Feature complete and ready for production use.
First off, thank you for considering contributing to gorollout. Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
4
+
5
+
Keep an open mind! Improving documentation, bug triaging, or writing tutorials are all examples of helpful contributions that mean less work for you.
6
+
7
+
# Ground Rules
8
+
9
+
This includes not just how to communicate with others (being respectful, considerate, etc) but also technical responsibilities (importance of testing, project dependencies, etc).
10
+
11
+
Responsibilities
12
+
13
+
* Ensure cross-platform compatibility for every change that's accepted. Windows, Mac, Debian & Ubuntu Linux.
14
+
* Code should be properly formatted using `gofmt`.
15
+
* Create issues for any major changes and enhancements that you wish to make. Discuss things transparently and get community feedback.
16
+
* Keep feature versions as small as possible, preferably one new feature per version.
17
+
* Semantic versioning will be used.
18
+
* Be welcoming to newcomers and encourage diverse new contributors from all backgrounds.
0 commit comments