Current method for reporting/tracking issues?
The preamble to this forum topic states "Before posting, please learn How to ask for support or report bug." That link takes us to a page that states "This page shows old instructions for MuseScore 2. For MuseScore 4 users, see How to ask for support or file bug reports." That link in turn simply returns a text search for that phrase (results that offer no real insights into the current process). At github.com/musescore/MuseScore, I am told to come here to the forum for guidance...so it's an infinite loop.
I'm sure I'm missing the obvious explanation, but perhaps somebody can provide the secret decoder ring? Thanks.
Comments
There are lots of infinite loops afoot these days.
Thanks for you interest in reporting. People like you help make the difference.
Here's a recent post about posting issues
https://musescore.org/en/node/361903#comment-1233584
scorster
In reply to There are lots of infinite… by scorster
Thanks much. Actually I had seen that one already, but there was no reason to think it was the definitive statement LOL. I remain unclear about the relative uses of this forum versus the GitHub discussion area. This all seems like yet another way to create duplicate threads. I probably should have been paying more attention when the context shift occurred. No doubt this is an improvement over the old issue tracker, but so far I'm mostly scratching my head. I guess I'll lurk for a while and see how the smarter kids are using the tools.