https://musescore.org/en/handbook/developers-handbook/release-notes includes changelogs of pre-release versions. It requires an extra click ("Release notes for MuseScore 3.x", "Release notes for MuseScore 2.x") to get to the release notes. It is also part of the Developers' handbook.
I think it would be good to have page which lists just the proper releases and it easily accessible for regular users. That is why I am in favour of keeping the "Roadmap" page.
The word "roadmap", however, usually refers to plans for future releases. So I would recommend changing the name of the page to "version history".
For discoverability, I would link the page from the front page, musescore.org.
I will create a new issue with this proposal later today. Do you agree with it?
Merge roadmap into version history
remove roadmap (as there is none for future releases)
add a filter to version history, by default only showing stable, but can be changed to include RC and/or beta and/or alpha
Which information does it contain that are not available in those other 2 places?
Which information does need to to get merged into what, and if so, why aren't you just doing it?
You right, I can do myself, I have seen that page long time ago, whith a slight smile.
Only surprised this mornint to see that thiw archive give question to people
And I answered ti Ribfog, regarding suggestions
Is this page is a real problem ? For common user ?
Comments
Roadmap should give future plans, that page which doesn't even mention 2.3.2 should be deleted for me.
Do we have an up-to-date page where users can look up version history?
If not, perhaps the best solution would to update this page.
In reply to Do we have an up-to-date… by RobFog
Yes, update, and may be rename.
But do not delete, it is the MuseScore history.
That's pretty much the same (but out of date) information as in https://musescore.org/en/handbook/developers-handbook/release-notes
In reply to That's pretty much the same … by jeetee
Not exactely, in releases notes page, the versions earlier than 0.9.6 are not there.
May be the merge of the 2 pages would be good.
https://musescore.org/en/handbook/developers-handbook/release-notes includes changelogs of pre-release versions. It requires an extra click ("Release notes for MuseScore 3.x", "Release notes for MuseScore 2.x") to get to the release notes. It is also part of the Developers' handbook.
I think it would be good to have page which lists just the proper releases and it easily accessible for regular users. That is why I am in favour of keeping the "Roadmap" page.
The word "roadmap", however, usually refers to plans for future releases. So I would recommend changing the name of the page to "version history".
For discoverability, I would link the page from the front page, musescore.org.
I will create a new issue with this proposal later today. Do you agree with it?
In reply to https://musescore.org/en… by RobFog
I really agree with this plan.
Thanks a lot.
See https://musescore.org/en/handbook/developers-handbook/references/versio…
It does have the same information and more, so https://musescore.org/en/about/roadmap can go
In reply to See https://musescore.org/en… by Jojo-Schmitz
At the difference that this page has no comments, Roadmap cannot go, I prefer the plan proposed before.
In reply to At the difference that this… by JLWaltener
Mm, I also unsure whether https://musescore.org/en/handbook/developers-handbook/references/versio… is the ideal solution. It includes a few release candidates and a beta. It also lacks information on versions older than 2.0b2.
In reply to Mm, I also unsure whether… by RobFog
Exactely
In reply to Mm, I also unsure whether… by RobFog
Merge roadmap into version history
remove roadmap (as there is none for future releases)
add a filter to version history, by default only showing stable, but can be changed to include RC and/or beta and/or alpha
In reply to Merge roadmap into version… by jeetee
Should be useful.
with a filter that a user can configure.
In reply to Mm, I also unsure whether… by RobFog
There is nothing missing from that page, prior to 2.0.b2 there were no tags on GitHub to link to, 1.x wasn't eveing using GitHub at all
The links to release notes are all available too via https://musescore.org/en/handbook/developers-handbook/release-notes
@lasconic disabled the ability to edit https://musescore.org/en/about/roadmap a long time ago, due to it being useless and superfluos
In reply to There is nothing missing… by Jojo-Schmitz
May be I am too nostasgic, and for fond memories, this page could be merged with others, or keep alive in an archive, or the MuseScore Museum...
In reply to May be I am too nostasgic,… by JLWaltener
Which information does it contain that are not available in those other 2 places?
Which information does need to to get merged into what, and if so, why aren't you just doing it?
In reply to Which information does it… by Jojo-Schmitz
You right, I can do myself, I have seen that page long time ago, whith a slight smile.
Only surprised this mornint to see that thiw archive give question to people
And I answered ti Ribfog, regarding suggestions
Is this page is a real problem ? For common user ?
In reply to Which information does it… by Jojo-Schmitz
Merged all links to announcements/notes from Roadmap into the Version information page as a link on the release date in the table.
All information that used to be in Roadmap is now merged out of it. Roadmap can be safely removed.
In reply to Which information does it… by Jojo-Schmitz
Thanks, @jeetee.
"why aren't you just doing it?"
I wanted to make sure I'm acting on consensus, didn't want to make changes that would be considered "disruptive".