Skip to content
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 a new release #166

Closed
jaraco opened this issue Oct 26, 2020 · 6 comments
Closed

Cut a new release #166

jaraco opened this issue Oct 26, 2020 · 6 comments

Comments

@jaraco
Copy link
Member

jaraco commented Oct 26, 2020

In #158, I encountered an issue that's been fixed in master. It would be nice to have a release that includes that fix.

@gaborbernat
Copy link
Contributor

At the moment only @FFY00 can do this 🤷 But we could do release 0.0.5.

@FFY00
Copy link
Member

FFY00 commented Oct 26, 2020

I would really like #132 to be fixed before a new release, which is not that straight forward because of the tests. But since there are major issues with the current one, I think we can defer it.

@pganssle
Copy link
Member

Presumably we should make the version 0.1.0? We've got major new features and in fact backwards-compatibility breaks.

Also, I think that at this stage in the project there's no reason to delay releases waiting on new features or bugfixes, as long as the version on master is an improvement on the released version.

@FFY00
Copy link
Member

FFY00 commented Oct 26, 2020

I am fine with that.

@gaborbernat
Copy link
Contributor

Agreed with @pganssle, we should release as often as possible until we reach 1.0.

@FFY00
Copy link
Member

FFY00 commented Oct 29, 2020

Just released 0.1.0 😊

@FFY00 FFY00 closed this as completed Oct 29, 2020
@pypa pypa locked and limited conversation to collaborators Jan 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants