Expectations for Latest MuseScore/master

• Apr 15, 2016 - 21:02

update: It turns out that after the upgrade to Qt 5.6 I might as well rebase (manually) my branch, because it won't compile now anyway. Oh well...

I have a branch of MuseScore where I have made small modifications to over 20 files in order to incorporate a feature. Any suggestions on how long I should wait to port my changes over to the latest major changes/upgrades? I'm simply trying to avoid multiple, manual merges of my code in so many files. I've already recently updated these same 20+ files, and it's a tedious process.

Am I simply being paranoid relative to @lasconic's message here, saying "Happy discovery of the new features (and the new bugs)"?

http://dev-list.musescore.org/Towards-MuseScore-3-td7579817.html

Yes, it is a feature I would love to see added to the master code base, but that's a separate discussion for when I've re-integrated it with these latest master changes, right? And maybe now isn't the best time to be integrating new features anyway, while the bugs get flushed out of this latest major set of changes.

I'm simply looking for some clarity on the developers' expectations, and some guidance for my own project. Thanks.

Comments

• Apr 18, 2016 - 13:52

Hi,

I don't expect any major rework in master soon, so any contribution can be done now and you will probably don't need to rebase your code much (if any, it should be easy). So, now it's the right time.

On a larger scale, it would be good if you file a feature request in the issue tracker so we have a place to discuss the feature you plan to add and a reference for the future.

Reply

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