List view
- No due date•8/8 issues closed
- No due date•34/34 issues closed
- No due date•20/20 issues closed
- No due date
- No due date•15/15 issues closed
- No due date•14/14 issues closed
- No due date•4/4 issues closed
- No due date•31/31 issues closed
- No due date•10/10 issues closed
- No due date•31/31 issues closed
- No due date•33/33 issues closed
- No due date•11/11 issues closed
- No due date•25/25 issues closed
- No due date•85/85 issues closed
- Due by December 18, 2019•8/8 issues closed
- No due date•20/20 issues closed
- No due date•12/12 issues closed
- No due date•9/9 issues closed
- No due date•4/4 issues closed
- No due date•23/23 issues closed
- No due date•3/3 issues closed
- No due date•6/6 issues closed
- No due date•18/18 issues closed
- No due date•49/49 issues closed
Binary compatible for all scala versions on most modules except cats-laws and cats-testkit.
No due date•43/43 issues closed- No due date•16/16 issues closed
- Due by January 22, 2019•42/42 issues closed
- No due date•64/64 issues closed
- No due date•1/1 issues closed
This is a placeholder for PRs that shouldn't be included in release notes.
No due date•132/132 issues closed- No due date•13/13 issues closed
Start a Scala 2.11 dedicated branching scheme: * Branch master - drops Scala 2.11, maintains is BC with 1.x * Branch scala2_11 - Scala 2.11 code New changes to master have to be ported to branch scala2_11 in a 2.11 BC compatible way and try to maintain as use site source compatible as possible - e.g. a new type class method added to master is added to a syntax trait method in scala2_11 branch. Release Cats 2.1 RC1 on both Scala 2.11 and Scala 2.12+ Note that 2.11 and 2.12+ code are NOT source compatible with each other, however, they will still maintain source compatibility with 2.0 and 1.x.
Due by November 15, 2019•71/71 issues closed- No due date•43/43 issues closed
- No due date•58/58 issues closed
- Due by December 25, 2017•3/3 issues closed
next release after 1.0
No due date•44/44 issues closedWe decided to have this final RC release
No due date•83/83 issues closedIncorporate all the API changes identified by the community with MF. Polish documentation to be 1.0 ready. We use this release to identify bugs that require binary incompatible changes. 3 months after MF, so likely Oct 2017.
Due by October 19, 2017•159/159 issues closed- No due date•2/2 issues closed
MF stands for final milestone. The main purpose/focus of this release is to offer a relatively stable API to work with prior to 1.0.0. It can be deemed as a proposal for the final API we are going to lock down at 1.0. Once released the community will then have some time to validate it. Note that unlike other libs, cats commit to maintaining binary compatible for a longer period post 1.0.
Due by June 1, 2017•173/173 issues closedInitial release of Cats!
No due date•2/2 issues closed