Beets master is approaching 1000 commits since the last release, and so I'm here to ask for a new release to be cut :)
I can help with testing if an alpha/preliminary release is cut
lovesegfault
All 2 comments
Hello! This post has more context on why releases are slow to come:
https://discourse.beets.io/t/forming-a-beets-core-team/639
The synopsis is that the project organization is currently bottlenecked on me to do releases, and I have somewhat extreme time constraints that make that hard. I'm still looking for help with this sort of thing if anyone wants to step up! :smiley:
sampsyo
on 17 Jun 2020
@nektro Please do not harangue maintainers.
Adrian maintains this wonderful piece of software for free, despite the fact that I'm sure his day-job keeps him quite busy. If things take time, it is what it is.
Trying to guilt him, or any OSS maintainer, into doing work on _your_ pace is wrong. Please reconsider your approach to collaborating.
lovesegfault
on 30 Oct 2020
Related issues
Freso
路
4Comments
Stunner
路
3Comments
ctrueden
路
3Comments
robot3498712
路
3Comments
myfreeweb
路
4Comments
Most helpful comment
@nektro Please do not harangue maintainers.
Adrian maintains this wonderful piece of software for free, despite the fact that I'm sure his day-job keeps him quite busy. If things take time, it is what it is.
Trying to guilt him, or any OSS maintainer, into doing work on _your_ pace is wrong. Please reconsider your approach to collaborating.