Was beta a bit too early?

• Feb 13, 2023 - 09:48

I don't want to sound negative here, but is this current MS4 beta really on par with a betta release level? I have never seen a beta version of a new version of software that would phenomenally crash so often as opposed to the previous version. My scores lose their specified volumes and panning almost every time a start a new editing session. Now it has become already like a habit for me to start any new session of working on my score by firstly restoring all the volumes and panning settings manually (!) Besides, every time when I open a file that I saved the night before, I am in fear and tremble to see that "the-file-is-corrupt-open-anyway" message, which if clicked on "open anyway" button won't result in anything - the file simply doesn't open. Now, in addition to recording (with a pen on a piece of paper) the new volumes and panning in the end of each editing session, I also have to save my file in .pdf format - to save all the latest modifications, which, if the file doesn't open again, I will also have to restore manually. I had none of such troubles in MS3.

I am sorry if I am coming across ranting. I fully realize that MS4 is a free piece of software and, thus, I have no right to complain. And I don't mean to complain. The new instruments, the playback and the interface of MS4 are just amazing! Instruments' sound improves daily and to me instruments already sound better than I could ever imagine - way way better than in MS3. Besides, at least, one issue that I had reported on GitHub has already been solved. So, the team IS working hard and I can only commend them for doing so. But I am a bit surprised by these crashes in the beta release. Do you think that they jumped the gun a bit with beta? Could all these crashes have been envisaged during the pre-beta days in the nightly builds? Or is it like the crashing problems became evident only after and thanks to the beta release? (my impression is that after the beta was announced the crashes have ironically become more often then during the pre-beta days)


Comments

In reply to by Jojo-Schmitz

"Simply 4.0.1"
- Then it looks like I have a wrong concept about what is beta and what is gamma. I thought that beta was all the versions starting from the point beta release is announced till gamma release is announced (that is, the release that is, unlike beta, has almost no bugs in it and could be ready for use by the broadest audience possible).

In reply to by innerthought

When people talk about alpha or beta versions, it usually means that they are pre-release versions. At some point it is decided that the stability and feature set is high enough for a normal release and you leave the Greek letter additions. That was the case for Musescore 4 on December 14, 2022. After that, bug fixes and feature enhancements will still be added in further releases.

Whether the software state at that time is already good enough to release it from beta will probably be evaluated differently. Is this different to other software products?

As noted, the beta is long over - that happened months ago. MuseScore 4.0 was released in December, and 4.0.1 after that, with 4.0.2 on the way. There is no current beta. The opportunity to report bugs during the beta - and thus before the release of 4.0 - has long has passed. But if you are finding bugs that you didn't find and report during the beta, it's not too late to report them now.

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