Git Product home page Git Product logo

Comments (48)

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024 1

Probably none, but these specifically have been merged to 3.x but not yet into master, this issue here is nothing but a reminder

from musescore.

MarcSabatella avatar MarcSabatella commented on May 14, 2024 1

This still feels like something that should be possible to automate completely. And to be perfectly frank, if it is to be done manually, it feels to me like the burden should fall on those who pushed for the change in the first place.

from musescore.

anatoly-os avatar anatoly-os commented on May 14, 2024 1

85 PRs left... The ones authored by @njvdberg have been merged successfully.

from musescore.

shoogle avatar shoogle commented on May 14, 2024 1

A heroic effort! (I was going to do mine myself but you got there first, sorry!)

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024 1

As far as I can tell 14 from 3.5.0 are still left to do

For most of my pending 3.x PRs I've now created PRs for master, see

from musescore.

ecstrema avatar ecstrema commented on May 14, 2024

I am not sure I get it. If all PRs solve a bug or add functionality, shouldn't they all get merged into master?
In other words, what PRs should be excluded from this list?

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

@anatoly-os is using his own book-keeping, so this issue isn't needed

from musescore.

shoogle avatar shoogle commented on May 14, 2024

List of PRs that have been merged into the 3.x branch:
https://github.com/musescore/MuseScore/pulls?q=is%3Apr+is%3Amerged+base%3A3.x

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

Whow, 165... (minus the ~30 listed above) and counting

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

@lvinken's PRs (4):

My PRs (36) (and their states) are:

To be continued (if and when more of my PRs get merged into 3.x), see #6079 (comment)

from musescore.

shoogle avatar shoogle commented on May 14, 2024

We can make the list more manageable by each taking care of our own PRs. My PRs are:

I will edit this comment to add any future PRs on 3.x, and to add "ported by #xxxx" when I create the corresponding PR on master. I will tick the checkbox when the PR is merged into master, or when we decide it is not needed (in which case I will add a comment to explain why).

That leaves these PRs that are not mine (and these are not mine or Jojo's). Anybody can view their own PRs here.

from musescore.

SKefalidis avatar SKefalidis commented on May 14, 2024

Ready to be merged to master (ported):

  • #6191 looks like a pretty innocent merge :-)
  • #6196 needs reviewing (but please don't make me rebase again after somebody adds more preferences)

Waiting to be ported to master:

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

@SKefalidis what about your #6198? Seems embedded into #6196, right?

from musescore.

SKefalidis avatar SKefalidis commented on May 14, 2024

@SKefalidis what about your #6198? Seems embedded into #6196, right?

Yes

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

We'd still need to check the PRs from

from musescore.

lvinken avatar lvinken commented on May 14, 2024

Like some other developers, I also maintain a private list of PRs to be synced to master. As I typically only work on MusicXML import/export, all my PRs apply equally well to master as to the current release.

As was mentioned before, having a public agreement on how we maintain such list could make the process more uniform and transparent.

from musescore.

shoogle avatar shoogle commented on May 14, 2024

@lvinken, let's not overthink this. I suggested a system that seems as good as any, but really it's enough to know that you plan to take care of your own PRs.

from musescore.

njvdberg avatar njvdberg commented on May 14, 2024
  • #6048
  • #6049 Merges cleanly into master.
  • #6060 Replaced by #6219
  • #6067
  • #6087
  • #6093
  • #6110 Merges cleanly into master.
  • #6116 Merges cleanly into master.
  • #6125 Merges cleanly into master.
  • #6129 Merges cleanly into master.
  • #6132 Merges cleanly into master.
  • #6144 Merges cleanly into master.
  • #6164 Merges cleanly into master.
  • #6180 Merges cleanly into master.
  • #6183 Merges cleanly into master.
  • #6216 Merges cleanly into master.
  • #6219 Conflicts, might be replaced by #6321 anyhow. Will check after this PR is merged.
  • #6221 Is a backport from master.
  • #6227 Merges cleanly into master.

from musescore.

MarcSabatella avatar MarcSabatella commented on May 14, 2024

I was under the impression that steps had been / are being taken to minimize the pain of the code formatting changes, by allowing things to be automatically reformatted. So only PR's that actually have semantic conflicts would need to be resubmitted manually.

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

I'm not sure whether there is sufficient track-keeping on which PR is needed for master too, hence this issue here. Those 170 PRs that went into 3.x is a large enough number for some of them getting lost and forgotten for master. Not all apply, some have been merged, some done differently, but there are enough left that need checking

from musescore.

shoogle avatar shoogle commented on May 14, 2024

I was under the impression that steps had been / are being taken to minimize the pain of the code formatting changes, by allowing things to be automatically reformatted. So only PR's that actually have semantic conflicts would need to be resubmitted manually.

PR #6363 has a script that does exactly this. It would be helpful if people could run it on their own PRs.

from musescore.

anatoly-os avatar anatoly-os commented on May 14, 2024

95 PRs left... At least, the ones enumerated above with unticked checkboxes.
I tick the checkboxes once I manually merge corresponding PRs.

from musescore.

MarcSabatella avatar MarcSabatella commented on May 14, 2024

Thank you for taking this on! I am certainly happy to handle any of mine that require work to rebase due to real changes in the code, but I am still hoping that the ones that can be handled more automatically can and will be. Most of mine are small and “libmscore-y” and can wait.

from musescore.

shoogle avatar shoogle commented on May 14, 2024

@anatoly-os, when merging PRs, watch out for the fact that PRs submitted before PR #6358 may show tests passing even though they have not been tested for coding style. Here's how to tell whether they have been tested.

from musescore.

MarcSabatella avatar MarcSabatella commented on May 14, 2024

Not merged for 3.x yet but presumably will be soon enough:

from musescore.

anatoly-os avatar anatoly-os commented on May 14, 2024

About 36 PRs left...

from musescore.

anatoly-os avatar anatoly-os commented on May 14, 2024

from musescore.

SKefalidis avatar SKefalidis commented on May 14, 2024
  • #6451 is the master version of #6450
  • #6423 is the master version of #6523 (not yet merged but will be soon I believe)

from musescore.

jthistle avatar jthistle commented on May 14, 2024

from musescore.

igorkorsukov avatar igorkorsukov commented on May 14, 2024

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

Is anyone continuing to work on the remaining ones?
Are there more that need to get added?

Here are mine:

from musescore.

vpereverzev avatar vpereverzev commented on May 14, 2024

#6546 Mine is actual for 3.x only, MU4 will rely on our new network module

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

OK I see, amended above

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024
  • #6818 - Porting 3.5.2_backend fixes to master

from musescore.

jeetee avatar jeetee commented on May 14, 2024
  • #6904 (master version of #6810) (cherry pick, libmscore only)
  • #6918 (master version of #6857) (cherry pick, libmscore only)

from musescore.

ecstrema avatar ecstrema commented on May 14, 2024
  • #6934 : Master version of #6933 --- No measure number shown when first staff is cutaway

from musescore.

MarcSabatella avatar MarcSabatella commented on May 14, 2024
  • #6899 - bad navigation after rest with content on last track

from musescore.

jeetee avatar jeetee commented on May 14, 2024
  • #6972 (master version of #6971) (cherry pick, libmscore only)

from musescore.

ecstrema avatar ecstrema commented on May 14, 2024
  • #6935 - Fix #214996: show measure number interval at multi-measure rests

from musescore.

ecstrema avatar ecstrema commented on May 14, 2024

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

from musescore.

igorkorsukov avatar igorkorsukov commented on May 14, 2024

from musescore.

Harmoniker1 avatar Harmoniker1 commented on May 14, 2024

Are all portable PRs ported as of this moment?

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

I think so, but would rather let @igorkorsukov and @vpereverzev decide (and then close this issue)

from musescore.

Tantacrul avatar Tantacrul commented on May 14, 2024

Closing due to inactivity and the fact that the issue is a year old. Let me know if it needs reopening.

from musescore.

Jojo-Schmitz avatar Jojo-Schmitz commented on May 14, 2024

As far as I can tell there are still open issues, stuff that need to get ported from 3.x to master, or at least been checked vor neccessity?

One example would be #6094 (port to master in #11462), mentioned in the initial list, but (errnously) marked as ported, unticked now

from musescore.

lvinken avatar lvinken commented on May 14, 2024

Checked the MusicXML issues still open in the Feb 15, 2021 comment: the fixes are present in master, no further work required.

from musescore.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.