Skip to content

Increasing file format tag to "4.10" #17402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from

Conversation

mike-spa
Copy link
Contributor

This is necessary because both PR #17001 and PR #17237 introduce new items and properties which can't be read by older versions.

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Apr 29, 2023

Gives a chance to merge #12133 too.

@cbjeukendrup said to have a list of things to consider when changing the file format...
Edit: Ah, here it is: #15705

@igorkorsukov
Copy link
Contributor

@mike-spa I think we should make new read implementation for format 4.1:

After, at 410 we will start removing the old unnecessary code for supporting old formats (it will remain at 400 and below) and we will add new code that we want to change #15705

@musescore musescore deleted a comment from Jojo-Schmitz May 17, 2023
@mike-spa mike-spa force-pushed the increaseFileFormatNumber branch from 1fffe54 to f8417aa Compare May 23, 2023 13:33
@mike-spa mike-spa closed this May 24, 2023
@musescore musescore locked and limited conversation to collaborators May 24, 2023
@mike-spa mike-spa deleted the increaseFileFormatNumber branch February 17, 2025 10:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants