Issue Tracker puzzle

• Oct 18, 2016 - 17:37

Does anyone know why I am seeing links to the same commit in the first post of two completely different issues (neither of which has anything to do with the subject of that commit!)? It seems rather odd....

Win7 Pro. IE11.

GIT COMMIT 1.png

GIT COMMIT 2.png

Attachment Size
GIT COMMIT 2.png 40.18 KB

Comments

• Oct 18, 2016 - 18:24

I actually had no idea that commit was for the latest stable version of 2.0.3.x; when I open that link I get a page entitled, "Update Languages", so I thought the commit was specific to that. Sorry, my lack of experience in fathoming the workings of github is obviously showing.

Thanks for educating me once again.... ;o)

Reply

• Oct 18, 2016 - 19:21

The idea is that when posting an issue, it usually helps to say what version of MuseScore you are using. Yes, we have the dropdown (albeit only as of recently) to select 2.0.3 versus 3.0-dev, but merely knowing someone is using a development build of 3.0 isn't specific enough - we like to know which build specifically they are using. That is why Help / Report a Bug automatically includes a commit link to identify the revision. Identifying builds by the commit link is convenient because it allows us to easily browse the source as it existed at that moment, or check to see if a given changed had been made yet. The content of that specific commit is not what is relevant; it's the fact that it identifies the state of MuseScore at the time of that build.

Reply

Do you still have an unanswered question? Please log in first to post your question.