statsmodels: RLS: Release 0.10/0.11/0.next blockers and schedule
statsmodels lack of releases is starting to cause a lot of problems. 0.9.0 will be 2 years old in 10 days.
What are the absolute must-fix issues before a release can be cut? There is a 0.10.0 project that I have mostly completed in the last week. There are a lot of milestone issues, but are there any that are must fix blockers?
This really needs a response from @josef-pkt since he knows the most about a lot of the areas that seem to have more reports (e.g., GLM). @kshedden anything that you see in the areas you contribute to? @ChadFulton anything you really need to get in soon (i.e., immediately)?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 7
- Comments: 38 (35 by maintainers)
@josef-pkt Ignore my previous – PyPI works fine using twine, so rc2 is now up.
Last comments on #5684 (which closes #5475) says it is ready to merge when green (and it’s green). Could be showtime.
Update/ETA? What can a a contributor do to help get this out the door?
Is #5475 the only issue that needs to be fixed before a RC can be drafted?
+1 for releasing now-ish and then updating dependency versions.
Any thoughts on the towncrier idea (or just doing what pandas does for whatsnew notes)?
It would mean the notes get written when things are fresher in memory and avoid having a monolithic task at release time. Hopefully that’ll lead to more regular, frequent, smaller releases.
I posted in response to your MixedLM question on stack overflow.
Regarding BayesMixedGLM, I don’t know about the API documentation, but you should be able to get what you need from the current source, below:
https://github.com/statsmodels/statsmodels/blob/master/statsmodels/genmod/bayes_mixed_glm.py
Nothing blocking for me, I would be glad to get a release out.
Per our policy discussed about a year ago on the mailing list, we are overdue for updating our dependencies, but I suppose we should instead do that immediately after 0.10 is branched.
I have no outstanding issues, thanks for all your work getting this done.
I am using a new feature to pin this issue since I feel strongly that this really needs to be resolved as soon as possible.