Cut new release #6
Comments
|
You may want to email him :) Also note that he could add both or one of us to the hex package ownership if he was comfortable with that with |
|
Can you publish prefixed package in the meantime? |
|
Sounds like @knutin will add @tsloughter and me as owners soon. Then we can cut and publish a release. We'll want to be sure the version reflects the breaking changes. Maybe 1.2.5 isn't dramatic enough. |
|
What is the breaking change? If it is not backwards compatible it'll have to go to 2.0.0. |
|
So the metrics callbacks changed or something? In that case then 2.0.0, if it is just removal of older OTP support than 1.2.0 is fine. |
- Per discussion on #6, set the version to 2.0.0 to reflect the breaking changes w.r.t. stats collection - Close #4 by mentioning 18.0 in README.md - Add more badges to README.md and pull out most of the sections into doc/overview.edoc (close #2) - Change "Eric Bailey" in LICENSE to "elli-lib team," since this is a team effort - Add Tristan to maintainers in src/elli.app.src
|
Yeah, instead of just |
|
We may want to come up with a solution for #13 first. |
|
What about this one: #14. Travis build fails but locally it's green ¯_(ツ)_/¯ |
|
Haven't had a chance to look at it, that'd be good too. |
|
@tsloughter and I have Hex rights now. Is there anything else we wanna do before cutting 2.0.0? |
|
Bump. I think we're good to go. What do y'all think? |
|
Let's do this 👍 |
|
Published 2.0.0. Please test and let me know how it goes. |
The elli-lib version has several improvements over the currently published version (1.0.5), namely wrt type naming collisions. I've merged
developintomasterand think it's good to go. The open issues either pertain to documentation or can wait.@knutin, would you prefer I open a PR to knutin/elli, or should we just publish from here? Also, by we, I mean you, since you're the owner of the Hex package. 😄
The text was updated successfully, but these errors were encountered: