Install packages I will deal with it for Mac and Windows. I will need help with testing but I plan to do ask on IRC. The plan is to support Mac OSX 10.7 and higher and on Windows, the installer should work from XP and up, but XP being not supported by Microsoft, and Qt supporting only Windows 7 and up, the software itself will be targeting these OS. If you have one of these, and want to help, contact me.
SplashScreen I believe Thomas will take this. Demos I would prefer to have an empty score for piano, or even a single treble staff with piano sound instead of a demo score on startup. Some demos like an updated version of Reunion or something to show off new features such as Swing, Parts, Tablature etc... would be great but would not hold the beta release. It would be best if the pieces are short. lasconic 2014-08-13 19:05 GMT+02:00 Marc Sabatella <[email protected]>: > I've been very much looking forward to this for a long time, and agree that > the time seems right! > > Bug fixing is of course a top priority, but one where I feel everyone > involved has a pretty good handle on what needs to be done. And in > particular, I have a pretty good idea of how I can continue to help. What > I'm less clear about are other tasks that would need to be done and how we > can help with those. There are half a dozen or so separate areas I can > think of that should probably be discussed. Maybe makes sense to have > separate sub-theads for each of these, but I'll at least summarize my > thoughts here. > > Beta announcement: I got bored on a plane trip recently and started to draft > up an announcement, intended to be suitable for the forum. Based on > whatever feedback I get, we could scrap it and rewrite, but hopefully just > tweaking would be needed. You can see and contribute to it here: > > https://docs.google.com/document/d/11-rEu0E0kaSKO82R63wJ3nky5zyfsf1w8Wj9VmL5CyQ/edit?usp=sharing > > We'll probably want to supplement this with a more high level press release > for the general public, and also with more detailed but still > quick-and-dirty how-to info on the new features. That leads naturally to > the next topic... > > Documentation: this is the biggest open area for 2.0. What some of you may > know but many pobably do not is that we have decided to have, in additional > to whatever documentation comes with the program and/or is available for > free on musescore.org, a separate more comprehensive manual available for > purchase (proceeds to help fund development efforts). I have been working > on that on and off for the past year, and will make a push to get this > finished by release of 2.0. Meanwhile, Thomas will be heading up efforts > for "community based" documentation (what ships with the program and/or is > available on musescore.org). > > Install packages: I suppose help could be used here? > > Templates: sounds like that discussion is going on in issue tracker > > Demos: I'd be happy to provide something "jazzy" to show off swing. Should > we plan on doing this for the beta? > > Startup: we've talked about new splash screens or startup screens - is that > still on the table? Anything anyone could be doing there? > > Bugs: for anyone not aware, I have been maintaining an organized "hit list" > of bugs that I think need to be addressed: > > http://musescore.org/en/issue-hit-list-marc-sabatella > > where issues listed at the top of each section in bold are the ones I > personally consider top priorities for beta (not that others aren't worth > fixing before beta too). It's just an informal list, but one I find useful > for tracking progress and my own peace of mind - making sure we don't > release anything with any glaring problems we knew about at one time but > forgot to deal with. If others have ideas about bugs submitted that are not > on this list that you think should be (keeping in mind of course that there > is no way every single bug in the tracker will be fixed before 2.0, much > less before beta!), feel free to let me know. Technically, anyone can edit > this file, but I'd prefer it be limited to adding to the list, and given the > frequency with which I update it (often several times per day) it probably > makes more sense to just contact me if you want to see something added or > bumped in priority (marked bold to indicate priority for beta). > > Marc > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Mscore-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mscore-developer > ------------------------------------------------------------------------------ _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
