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

Please Do a Bugfix Release #3639

Closed
adonig opened this issue Mar 22, 2019 · 9 comments
Closed

Please Do a Bugfix Release #3639

adonig opened this issue Mar 22, 2019 · 9 comments

Comments

@adonig
Copy link

adonig commented Mar 22, 2019

Sadly the current version of pipenv available in homebrew has broken support for pyenv. While it's possible to install pipenv from master, it would still be a good idea to release a new version as soon as possible. Otherwise you risk that people who try pipenv for the first time might get a misleading first impression. Additionally even seasoned pipenv users suffer from having to do a web search to find a workaround to fix their work environment.

@whyboris
Copy link

It also seems it's time to have a proper regular Next Release according to the Project Board:

https://github.com/pypa/pipenv/projects/8

The only issue in the project board not in the Done column has already been closed: #2359

We've not had a release since Nov 26, 2018 and it's end of March 2019 (4 months). I suspect enough things have been improved/fixed since then that many people are still running into trouble they could be avoiding with just the latest release 🤔

Thank you for your work 🙇

@techalchemy
Copy link
Member

To be fair, I have no idea what that project is -- apologies for the delay on this but we had significant delays getting CI builds passing with updates to pip, piptools, and other resolver issues. Each delay has added up to over a week at a time and this is a project that happens in our free time -- and it is super complicated to push a release with so many moving parts coming together. I will get one out this week, which is about a week or two behind when I actually planned to cut a release.

@AlJohri
Copy link
Contributor

AlJohri commented Apr 9, 2019

Thanks for the hard work @techalchemy. Also looking forward to restoring pyenv support. ❤️

@miketheman
Copy link
Member

Hi wonderful contributors! Is there any chance this is in the works, or could use some help getting things ready for release?

@AlJohri
Copy link
Contributor

AlJohri commented May 22, 2019

Related: #3742

@amir-barkal
Copy link

amir-barkal commented May 29, 2019

why you no?

(Thank you for your hard work!)

@whyboris
Copy link

@amir-barkal -- it's very likely you meant the image in a jovial fashion (it's a funny meme, I like it too), but it's easy to misread people on the internet, and the maintainers of the repository might feel as if you're demanding they do something (which isn't pleasant).

In the future, a comment like this accompanying with a comment below saying something like "thank you for your hard work 🙇‍♂️" would remove the ambiguity 😉

@amir-barkal
Copy link

Apologies to anyone if I have offended them, that was never my intention.

@whyboris I’ve edited the comment as per your kind advice. Thank you.

@frostming
Copy link
Contributor

Redirect #3742

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants