Annotate "Release notes" to indicate that the handbook needs to be updated.
Where a new feature, fix etc. in an upcoming MS release requires a handbook update, perhaps this could be indicated by an annotation at the end of the relevant entry on the Release notes page. Maybe use (Handbook) or (H) or [H] or something similar?
Comments
Good thinking! To keep it from being visible on the front end, how about a faux HTML thing: < handbook / > I'll make a start on that. EDIT: Done.
In reply to Good thinking! To keep it by Isaac Weiss
Del.
So, is the idea to update the handbook with a line such as
Starting in MS2.1 Double click the instrument name to edit. Once changes are made, press the escape key or click outside the edit box to accept changes.
Once that is done, what do we do? Let Isaac (or someone) review it and delete the hidden hashtag?
In reply to So, is the idea to update the by mike320
Once that is done, you can go delete it from the release notes yourself. But let's not do this until at least there is a release candidate.
In reply to Once that is done, you can go by Isaac Weiss
Right
FWIW, this is what I was getting at in https://musescore.org/en/node/164551#comment-636801, but no one seemed to think much of the idea then :-)
In reply to FWIW, this is what I was by Marc Sabatella
This time around the idea was a lot more concise, proving that when eating an elephant one should take one bite at a time. ;-)
The annotation needs to be visible on the page itself. And it needs to be understandable by everyone – not just programmers.
In reply to The annotation needs to be by geetar
But there will likely be a brief period after 2.1 is out, and the release notes are official, when we're still working to update the documentation—and certainly at that time people should be able to get the clean release notes without any work-in-progress labels.