Pipenv: New release?

As a collaborator without release permissions, I can't give much help. As far as I know, Dan was trying to triage plenty of upstream issues and make an automated release pipeline, moreover, as you know, PyCon happened then.

However, putting such words upon open source devs who spend their spare time on such a complex project is not cordial at all while I admit there some room to improve for the release processes. Suggestions are welcomed but not sarcasm.

I will keep this issue open for any followers who are confused.

Hi @frostming,

No sarcasm was indented. I much admire pipenv team and Dan in particular (and I believe he knows it since we spent plenty of time in comments in pipenv issues). If any of you consider my original message as offensive - please accept my sincere apologies.

The concern behind my message was about release cadence - pipenv was regularly released about once a month until last November. Then releases stopped which is quite puzzling considering the project is very actively developed.

Release cadence came to a super dramatic halt because of a _lot_ of
upstream issues (pip broke, setuptools broke, then pip and setuptools both
released breaking fixes, and we have about 15 upstream dependencies which I
personally maintain and which need to be fixed to support a pipenv release)

I am currently cutting releases of the last 2 assuming tests pass, so that
we can refocus on cutting a pipenv release now.

Apologies for the delay, but the issue backlog is quite long and I am
definitely not excited about triaging

On Mon, May 13, 2019 at 10:08 PM Zaar Hai notifications@github.com wrote:

Hi @frostming https://github.com/frostming,

No sarcasm was indented. I much admire pipenv team and Dan in particular
(and I believe he knows it since we spent plenty of time in comments in
pipenv issues). If any of you consider my original message as offensive -
please accept my sincere apologies.

The concern behind my message was about release cadence - pipenv was
regularly released about once a month until last November. Then releases
stopped which is quite puzzling considering the project is very actively
developed.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pypa/pipenv/issues/3742?email_source=notifications&email_token=AAHI7RSHQI4TERBQIH5BLA3PVINJDA5CNFSM4HMOYEP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKBTMY#issuecomment-492050867,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHI7RRQMB7BX3UV3ZHPBX3PVINJDANCNFSM4HMOYEPQ
.

Thanks for the info Dan and and thanks again for all your great efforts!

On Tue, 14 May 2019 at 16:45, Dan Ryan notifications@github.com wrote:

Release cadence came to a super dramatic halt because of a _lot_ of
upstream issues (pip broke, setuptools broke, then pip and setuptools both
released breaking fixes, and we have about 15 upstream dependencies which I
personally maintain and which need to be fixed to support a pipenv release)

I am currently cutting releases of the last 2 assuming tests pass, so that
we can refocus on cutting a pipenv release now.

Apologies for the delay, but the issue backlog is quite long and I am
definitely not excited about triaging

On Mon, May 13, 2019 at 10:08 PM Zaar Hai notifications@github.com
wrote:

Hi @frostming https://github.com/frostming,

No sarcasm was indented. I much admire pipenv team and Dan in particular
(and I believe he knows it since we spent plenty of time in comments in
pipenv issues). If any of you consider my original message as offensive -
please accept my sincere apologies.

The concern behind my message was about release cadence - pipenv was
regularly released about once a month until last November. Then releases
stopped which is quite puzzling considering the project is very actively
developed.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<
https://github.com/pypa/pipenv/issues/3742?email_source=notifications&email_token=AAHI7RSHQI4TERBQIH5BLA3PVINJDA5CNFSM4HMOYEP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKBTMY#issuecomment-492050867
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAHI7RRQMB7BX3UV3ZHPBX3PVINJDANCNFSM4HMOYEPQ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pypa/pipenv/issues/3742?email_source=notifications&email_token=AAAOGWM67SNCKMTOBNG2NXDPVJNYFA5CNFSM4HMOYEP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKNYZY#issuecomment-492100711,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAOGWLGL74UNBTKP4AORX3PVJNYFANCNFSM4HMOYEPQ
.

--
Zaar

Want to thank you dudes for all the hard work you put into the ecosystem its much appreciated!

I'd like to gently nudge this thread since I'm now stuck behind two vendored bugs #3382 and #3757

Is there a place we can watch for passive status updates @techalchemy on the vendoring situation?

Ed- I realize I could watch the PRs, I meant status updates in a way those of us less familiar with the project could get

@techalchemy Is there anything we can do as users to help test that would reduce the burden of a release? I use pipenv every day and would be happy to help if possible.

@techalchemy bumping this thread because my team is stuck behind some of the VCS bugs in the current release. Anything you need help with to get the next version to release?

We are 634 commits behind the latest release which was 10 months ago now.
Could we please have a new release?
I humbly request that this becomes priority number 1 🙇

I agree. The release cycle is running five months behind at this point. @techalchemy hasn't been active recently so someone else from pypa may need to help us out here. @nateprewitt or @kennethreitz can you help us get a new version out?

EDIT: Sorry, @uranusjr too. I just found the official maintainer list.

People wating for a bugfix release may want to try https://github.com/sdispater/poetry in the meantime if it fixes their issues.

@techalchemy @nateprewitt @uranusjr @kennethreitz is there anything we can do to help publish a new release?

EDIT: adding @frostming

I spoke with @techalchemy in IRC today and pipenv now has an update in https://github.com/pypa/pipenv/issues/3369#issuecomment-594875477 (including some issues people can help with to expedite the release).

@thieman hi and hope you're doing well! And thanks to everyone who commented in this issue.

Pipenv is working toward a new release -- see #3369 for specific details. The goal is to get that out this month.

I helped @techalchemy write a new update email he's just posted on distutils-sig (mirrored on the pypa-dev list). Dan notes:

As some of you may already know, I recently changed jobs and am now working for Canonical where I have part of my time allocated to open source work in general (and pipenv in particular).

So: thanks, Canonical!

Dan's email also includes a few ways you can help, directly and indirectly, to expedite this release.

@frostming I'm inclined to close this in favor of #3369, but I defer to you.

@techalchemy is working towards a release right now with the PR #4169. How others can help:

• replying to new users' questions in pipenv's GitHub issues
• helping develop a "Pipenv workflows to test" list, along these lines
• retweeting this tweet about the current status and how people can help
• improving our release process -- @techalchemy has started a Pipenv release process instruction guide -- if there are steps that should be in there and are not, please comment in #3369 or add some bullet points in that document
• volunteering to test on Windows

I'm going to go ahead and close this as a duplicate of #3369 but thanks to everyone for your comments and concerns!