-
Notifications
You must be signed in to change notification settings - Fork 171
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
Cut 1.0 release #260
Comments
No objection but I would really appreciate it if we could decide whether to merge this first: #246 (support isinstance and enums) |
Let's cut the 1.0 release prior to merging #246 and maybe consider merging for a subsequent 1.1.0 release. |
I just released 1.0.0. |
Woot. Thanks @ogrisel
…On Mon, May 6, 2019 at 6:40 AM Olivier Grisel ***@***.***> wrote:
Closed #260 <#260>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#260 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACKZTAAW4DQKYXNMD2QX53PUAKKVANCNFSM4HENR3FA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Any objection to bumping the release to 1.0 next time around? There are a variety of reasons to do this, but the best I've heard is that some institutions have a hard time justifying using software with a version number less than 1.0 to their IT administrative staff.
The text was updated successfully, but these errors were encountered: