General Discussion of MuseScore 2.0, the Trunk and the 'Nightlies'
I would like a place to discuss -- strictly from the end-users’ viewpoint -- the Nightly Builds as they are released, I know I’m not the only one who’s interested in testing them out, and I think that sharing information and commentary would be valuable for all of us who share this concern.
In my own experience, R.4309 was remarkably stable and powerful. A couple of successive Nightlies were not: one of them prompted me that it couldn’t run without DLLs that were apparently missing, and one of them couldn’t even be unzipped from the archive.
FWIW -- I’m using Windows XP with SP 3.
Anyway, I continued to use R.4309 -- and have been preoccupied doing ‘real’ work with it. I haven’t been paying attention to Nightlies since my experience with the dysfunctional ones I mentioned, but I did download the most recent one today -- R.4377.
At least I could extract it with 7-Zip, and it passed the test of opening a file, saving the file, and then quitting the program gracefully. Unfortunately I won’t be using it, as it reformatted my fingering text when I reopened the file. Even when I went back to 4309 and saved my Text Styles, I wasn’t able to load them into the file when I reopened it in 4377.
In fact, text behavior seems to have regressed between these two releases. The context (‘right-click’) menu in 4309, which included ‘Set Invisible’ and a ‘Text Properties...” option that led to a dialog box from which Styled/Unstyled could be manipulated, has been truncated in 4377 to remove both those options.
Of course, perhaps that’s temporary -- but not a good thing, nevertheless, for my own purposes.
The point of this post is that I’d like to solicit other members -- those who have the same curiosity (and temerity!) that I do about ‘beta testing’ the unofficial releases -- to do so regularly and to have a place where we can actively post about them (i.e., our perceptions of the features that seem projected to be included in version 2.0, the direction in which those features seem to be developing, issues of stability (obviously), other problems might we see (or foresee), etc.).
I started a thread similar to this one a few weeks back, and the response was ... subdued. An ‘official’ response was that the best place for these concerns was in the ‘Feature Request’ area of the forum -- but I disagree. I honestly got the impression that on-going discussion of the Trunk that will become 2.0 -- at least by MS users like me -- was not encouraged.
I understand all the points that have been made about ‘no guarantees’ with untested Nightlies -- whether about performance, stability and features or whether any functionalities will even survive to be incorporated into the next major release. And I think all of us accept those caveats and expect those limitations when we download and use the Nightlies for any reason. The disclaimers are there, and we understand their implications. I also understand a point made by someone that the development of MuseScore ‘isn’t a democracy’ -- something that goes without saying and might well have been left unsaid.
But still -- I don’t really see the point of regularly releasing the Nightlies if the developers don’t wish to encourage people to test them, talk about them or to provide a dedicated place for that discussion to take place. I propose the need for exactly such a place, and perhaps this very thread can serve that purpose.
The last time I aired these concerns, Mark Sabatella immediately responded with his substantive agreement. Mark, are you out there? Anybody else? I honestly think that the MuseScore ‘community’ can (and should) embrace those of us who -- while not developers ourselves, and while explicitly recognizing that any of our feedback may or may not have any bearing whatsoever on what choices the developers make -- might like nonetheless to have a dedicated place to discuss the future of MuseScore..
Sorry for the length of this; thanks for reading; all thoughts and comments on this subject are appreciated!
Comments
I'm here. My impression is that now is not a particularly good time to be worrying about the nighty builds, for several different reasons. The main one is the major code restructuring Werner has mentioned, trying to separate the GUI components from the underlying engine. Another is the fact that some of the focus right now is diverted to the branch that will become 1.x. So I would expect the nightly builds to be less stable than usual right now.
However, I do agree that it would be nice to have a forum for users like us to discuss issues, new features, and so forth specifically as they relate to the nightly builds (or other unreaeased versions). I think the most obvious way to do that is to simply create a new forum, called "Nightly Builds" or something more generic. Then those discussions needn't clutter the existing forums. Yes, there is the developer's mailing list, but I think you and I are talking about something more user focused than that.
I guess we need to consider the current state of the trunk is not at the stage that issue reporting is very useful. Parts of the trunk are still heavily being refactored which can break the nightlies completely. So my view is to give the developers their time and ask them to report back when they feel the time is right for stability testing.
In reply to Release cycle phase by Thomas
but I would still raise the question of why Nightlies are made available to us end-users so frequently then -- or perhaps made available at all (i.e., for what purpose, exactly?)
And even if the reporting of issues isn't useful to developers, the sharing of issues is, I think, very useful to those of us who are exploring the potential to actually use the Nightlies and care about the direction of development.
For example, as I wrote earlier:
R.4309 was great -- for me, anyway -- but that released some time ago now..
R.4377 -- the current one -- isn't usable for me at all.
I'd like to know what happened in-between! There have been quite a few releases between 4309 and 4377, and I can't help being curious about which might be a useful 'upgrade' for me ... and which ones would be a complete waste of time.
Seems like a place for us end-users to talk about this stuff amongst ourselves would been the only place to share that information. So if not here, then where? How about a Facebook group?
In reply to That seems reasonable ... by [DELETED] 448831
Good points. One of the advantages of a forum would be so people wouldn't feel the need to submit issues prematurely - they could just note them in the forum, and other users would know what to expect. But still, it also seems we should let them get to a place where they think things are more stab;e before rocking the boat further.
I wouldn't be opposed to a Facebook group, but that sounds like just one more thing to have to check up on, and I've got more than enough of those already.
In reply to Good points. One of the by Marc Sabatella
Face book would mean loss of time and space (more than 50 % of the screen is used for non relevant topics)
Some Google group would be more adequate. But 2 musescore forums dedicated to nightly build should be convenient.
One forum for trunk, one for fork
In reply to Face book would mean loss of by robert leleu
Robert, I don't think I understand what you mean about two forums dedicated to nightly builds.
In my limited experience, the nightly builds that are made available via the Download page have all been works-in-progress toward 2.0 (i.e., the Trunk).
Have I misunderstood or missed something? For example, are there nightly builds presently available for the upcoming version 1.1 as well?
Technology Preview is a collective name for trunk, nightly, ... It's terminology used by the Qt project.
You can find this new forum at http://musescore.org/en/forum
Enjoy!
In reply to Technology Preview forum added by Thomas
Thanks, Thomas - I think this will prove very useful!
I sometimes wonder whether nightly builds should be available. Although testing is essential, the code can change at any time. I think perhaps until Werner is finished the on-going development (general features and existing bugs - listed or otherwise) and asks people to test it, they shouldn't be available (maybe just temporarily) - my arguments though:
1) If something was handled incorrectly, but thought to be fine - it could take a lot of reworking to correct.
2) Something marked as fixed, but not (subsequently forgotten/assumed to be fine).
3) If someone needs the latest fixes for their work.
Now I'm not sure!
Maybe until the code transfer is finished at least, they should be held off? It would stop tempted people (myself included) to file issues, when some could be just temporary.
In reply to I sometimes wonder whether by chen lung
The phrase "use at your own risk" must not be getting through to some. Your statement "or if someone needs the latest fixes for their work" should never be spoken because you are not supposed to be using the nightlies for anything but testing and playing with. It's that simple.
Through the nghtlies, I am able to see the direction that the development team is taking things and I see exciting things happening! Unless the nightly is completely broken or unusable I generally don't report anything. I think issues that cause crashes in the nightlies are important and likely should be reported, the rest can wait until the code gets more stable. Then we start hammering the features into shape.
As Thomas said, lets bring this discussion into the new Forum group and close this one off.
In reply to Not for use by schepers
Quoting Download : "They are intended for testers and advanced users who want to experiment with the newest features or need access to the latest bug fixes and are willing to risk the instability of an unfinished product."
In reply to Quoting download: "They are by chen lung
I feel so dumb right now, but apparently I'm having a 'senior moment' or something -- as I can't remember the answer to something I'm sure I knew (or should know):
It appears that at a given time, a handful of the most recent Nightly Builds are available in chronological order.
But is there anywhere on the site that ALL of the previous nightlies are available? I've mentioned how impressed I was with R.4309, for example --- but it's long gone from that list. (I still have the zip file I downloaded originally, but what if I needed it again? Or if others were interested in that specific pre-release?)
Oh wait ... something's coming back to me. Are the files stored somewhere on the Source Forge site?
And A BIG THANKS for creating that new sub-forum!
In reply to A new sub-forum, great! And one question ... by [DELETED] 448831
Nightlies are not stored. If you want to have a certain revision back, you need to compile MuseScore yourself after checking out the right commit.
In reply to Quoting download: "They are by chen lung
And your point for quoting the nightly page is? It doesn't detract from what I said. Experimentation and "risk" do not equate to using an unstable build for serious (non-experimental) work. I think it's very foolish to try and use the nightlies for anything other than testing. That's the general thrust of the wording of the download page.
While I am sure Werner is producing the Goldberg project under MS 2.0, and the development team will try to keep existing 2.0 files compatible with future 2.0 versions, I would not put much faith in the efficacy of the nightlies until the team feels it is ready for such use.
In reply to Your point? by schepers
The download page said about people who in addition to testing, may wish to access to the latest fixes. I assume this means there's some fixes it would be alright to discreetly make use of (someone may urgently require it for something), if you know what you're doing (I'm thinking more for export purposes - printing etc).
This doesn't mean I recommend it for general use, because it is on-going development (all my work is created/saved in 1.0).
In reply to Your point? by schepers
FWIW, I suspect the wording in question was meant to be general in nature and not to only apply the current situation. I'm sure there are times when the nightlies *are* a good way to get the latest bug fixes. I'd take advantage of one if I needed some particular feature to complete a given project where I just needed to get printed output, even though I know it might not be stable for continued use, and indeed the file might not be openable in the next version.
But, the current nightlies are apparently not in that category.