Get ready for RC2 - #2044
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2044 +/- ##
==========================================
+ Coverage 94.58% 94.66% +0.07%
==========================================
Files 325 328 +3
Lines 5507 5533 +26
Branches 220 199 -21
==========================================
+ Hits 5209 5238 +29
+ Misses 298 295 -3
Continue to review full report at Codecov.
|
|
Awesome @LukaJCB. I can draft the blog post unless you want to. I am thinking of giving a quick overview how we get here and our commitment to compatibility and community building going forward. |
|
If you draft the blog post, that'd be absolutely great! Im sure we could collaborate to create a really good one! |
|
great I'll start one tomorrow. |
|
Do you want to also update the AUTHORS.md? Or I'll be happy to do that. |
|
Sure thing, will do! Is there a good way to find out who's a new contributor, or do I have to do it manually? :) |
|
I used some scala code to do that one time, and the next time I lost that code so I did manual. Not much difference in terms of time consumed. |
|
Alright then 😁 I've also written up something for the blog post, will you create a PR to the Typelevel blog, or should I do that? |
|
I am also drafting. |
|
also are we determined to wait for #2046? |
|
I think we should wait for it, yeah. If needs be, I can get it done on the weekend :) |
|
I'd say we set the deadline for these kinds of PRs for Monday. WDYT? :) |
7d003c0 to
643a00f
Compare
643a00f to
a05d42f
Compare
kailuowang
left a comment
kailuowang
left a comment
There was a problem hiding this comment.
we don't have a migration guide, but I think we can wait until 1.0 release.
* Add grouping to scaladoc for arity methods This makes it so when you look at the `Applicative` scaladoc you don't have a bunch of `ap3`, `ap4`, etc noise mixed in with the more meaningful methods. Instead, the generated higher-arity methods show up in separate scaladoc groups below. To see the changes you can pull this branch, run `sbt unidoc` (you may need to clean first), and open `cats/docs/target/scala-2.12/unidoc/cats/Applicative.html` in your browser. * Add doctest examples for Apply (#2086) * Get ready for RC2 (#2044) * Draft release notes * Update * Update * Update * Update * Update * Update Authors * Update * Update * Update * Update * update * Update * Update CHANGES.md * Update AUTHORS.md * Update README.md * Update deprecations to product{L,R} instead of ap{L,R}
* Setting version to 1.0.0-RC2
* Setting version to 1.0.0-SNAPSHOT
* Update deprecations to product{L,R} instead of ap{L,R} (#2121)
* Add grouping to scaladoc for arity methods
This makes it so when you look at the `Applicative` scaladoc you don't
have a bunch of `ap3`, `ap4`, etc noise mixed in with the more
meaningful methods. Instead, the generated higher-arity methods show up
in separate scaladoc groups below.
To see the changes you can pull this branch, run `sbt unidoc` (you may
need to clean first), and open
`cats/docs/target/scala-2.12/unidoc/cats/Applicative.html` in your
browser.
* Add doctest examples for Apply (#2086)
* Get ready for RC2 (#2044)
* Draft release notes
* Update
* Update
* Update
* Update
* Update
* Update Authors
* Update
* Update
* Update
* Update
* update
* Update
* Update CHANGES.md
* Update AUTHORS.md
* Update README.md
* Update deprecations to product{L,R} instead of ap{L,R}
* Setting version to 1.0.0
* Setting version to 1.0.1-SNAPSHOT
* Setting version to 1.0.1
* Setting version to 1.0.2-SNAPSHOT
4 participants
We're really close to 1.0, so I decided to draft some release notes. I think it'd be great if we could also get a blog post on typelevel.org in time as well. :)
Only have a couple of tickets still open:
liftFand addliftKto transformers standardise onliftFand addliftKto transformers #2033And then we have a couple of others that break bincompat so we should think about including them in 1.0.0