-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let's talk the next release (again) #594
Comments
I'm fine with doing this now. As far as I know, things are in a relatively coherent stage. Some future release milestones I can think of are:
I don't think 0.3.0 needs to wait for any of these, I just wanted to let you all know what was on my mind. |
I have already said so on Gitter, but just for to make it official, 👍 for an immediate-ish 0.3.0 release. |
I'm a fan of "release early, release often", so 👍 from me. |
I've gotten bogged down in circe stuff the past couple of days, and now that 0.2.0 is out this is less urgent for me, but I haven't forgotten my promise to write up release notes. 😄 |
This was fixed by bea10d9 and can be closed now. |
This is a follow-up to #486, and some of the conversation there (and on Gitter this morning) is relevant.
A lot has happened since 0.2.0, and there seems to be general agreement that we're ready for an 0.3.0 release. From my (totally selfish) perspective there's no real need for this to happen before Shapeless 2.3.0, which I'm waiting on for circe 0.2 anyway.
If there are particular issues that people would like to see resolved before 0.3.0, maybe it would be a good idea to attach a new milestone to them? Otherwise I'm happy to start putting together a draft of release notes for review.
The text was updated successfully, but these errors were encountered: