transparency is required in order to get any feedback worth mentioning. without any info from you providing feedback is futile exercise
* actual data on what's been already worked on and what's the order/importance of each of the features being worked on.
* what's coming in 4.x, what bugfixes, features?
* when's next 4.x arriving if ever, or this is it and we should not expect next 4.x
* what's coming in 5.x, what changes, what features?
* when's 5.x coming
feature-request part of the forum is "full" with clear features, on top of that, some "more modern" g-code generation ... e.g. long sequences of very short movements in the GCode (something all modern slicers fixed)
What I fail to understand is that you are not taking the "low hanging fruits" .. there are so many features missing that are easy fix that would make a lot of users happy and solve the "no release in 2 years" problem .. e.g.
- connexant 3d mouse support (approx one engineer/day to implement, another one to test)
- octoprint integration (2 eng/hours to implement, 10 eng/minute to test for basic implementation, 2 eng/day to implement full fancy set of features)
- RRF (duet) integration (2+2 eng/days to implement)
- import/export all settings/profiles as xml/json/whateverhumanreadable (?! a week?)
that's like tops 2 weeks of single developer's work on super safe stuff that does not pose risk to the system (no chance of introducing bugs if a developer is not a total dunster) and you have a release .. There's bunch of stuff like that ... you can do a release every few months .. but when you, like now, wait 2 years to make any update, expectations will always be higher than what you can deliver