A while back we did some planning for the 1.3 release. The original target is visible here: https://dev.funkwhale.audio/groups/funkwhale/-/milestones/5#tab-issues
Now, some time passed. And we did a lot of work, its amazing to see all those closed issues and it was great work, what a rush! So at first, congratulations to everyone making this happen. Amazing 🥳
Now we have the situation that we basically reimplemented the whole Frontend. A lot of other changes and bug fixes are already merged to develop as well. But when I check the amount of remaining issues, it feels like it would take as long as we already worked on 1.3 to actually ship it. And I do think this is a problem.
At first, we get quite some bug reports which are already fixed in develop, and people experience those issues every day. Also, until we release 1.3 we have to maintain 1.2 as well, which has some general issues (no Python Dependency Locking for example) which causes issues from time to time forcing us to apply another dirty fix.
So I would suggest to cleanup the 1.3 milestone, basically freezing features and we start working on releasing 1.3 to the world, giving people a great new version and move all remaining issues to a 1.4 milestone, which then can be release a bit faster eventually. What do you think?
@mjourdan @Sporiff @petitminion I remember when I started the discussion a few month ago in our maintainers call, we decided against lowering the amount of issues for 1.3. But I think we should reconsider this, since I doubt we can maintain 1.2 and 1.3 in the long run and its a risk for us not to release sometimes soon.
Please not, even if we remove tasks from 1.3, its still a lot to do to actually release it.