Maybe I can shed some light on this.
I used to have more time for KiCad, I used it more and I followed the development intensely. This can be seen especially in the thread Post-v5 new features and development news where I had something to say about most of small and large new features and also about what else was happening in the world of KiCad development.
I don’t regret what I did, but later I have seen that publishing everything what happens may cause some kind of inconvenience for the developers. They don’t have as much peace for their work as they might need. Especially when a large new feature is committed to the codebase, the developer may already know it needs this and that before it’s ready to be tested “reliably”. Publishing the brand new feature widely among end users right away when it’s introduced to the code base may lead to unwarranted criticism and some unhelpful bug reports.
Therefore, today I might be a bit more careful about announcing development news, case by case basis.
This doesn’t mean discussion about new features, whatever they are and no matter how some user have found them and tested them, would be improper. It just comes with the caveat that there may be known bugs and the situation may change in rapid pace.
Then there’s the other side to this. First, KiCad unstable development code base is meant to be tested. This is how the whole ecosystem works: new features are developed publicly in the “master” branch which is then built daily and published officially as “nightly builds”, and feedback is wanted. This wouldn’t make sense if discussion about it would be somehow discouraged or forbidden.
Second, there’s a kind of 2nd tier of new features which developers want to integrate to the code base but so that they don’t want to give an impression that it’s ready to be tested widely quite yet. A feature can be put behind an advanced configuration flag so that the feature is built in but is activated or revealed run time only if the corresponding flag is set in a special configuration file. So, if a developer really doesn’t want to spend time on public discussion or bug reports of some unfinished feature, they can commit it but make it “hidden”.
Third, there’s no better place for discussion about KiCad development without interfering the developers’ work than this forum. You just have to understand that if someone else than a developer answers here, it doesn’t have the same authority than a comment by the developer who is working on the feature.
In short: discussion is welcome, use your common sense, don’t expect new features being ready and polished when they are introduced or published. You can always ask in the forum. Don’t pollute the development mailing list or the bug database with questions which can be answered here. Be aware of the caveats of this forum – for end users by end users, only occasionally and unofficially by the developers.