Skip to content

Conversation

@cristianoc
Copy link
Collaborator

@cristianoc cristianoc commented Jul 18, 2022

Any new bug fixes until first real release will be merged onto this branch.
Meanwhile, 10.1 features will be merged into master.

@cknitt
Copy link
Member

cknitt commented Jul 18, 2022

Can you run scripts/setVersion.js to update the version in all places?

@cristianoc cristianoc force-pushed the 10.0_release branch 2 times, most recently from e5f3d86 to e14a754 Compare July 18, 2022 06:55
@cristianoc cristianoc changed the title Branch for release 10.0 Branch for release 10.0 [Do Not Merge] Jul 21, 2022
@cristianoc
Copy link
Collaborator Author

@TheSpyder any more comments/suggestions on the release notes?

@TheSpyder
Copy link
Contributor

Only one, and I’m on mobile so I can’t easily suggest changes.

the mentions of adding @val include extra square brackets, making it [@val] which I don’t think is right

@cristianoc
Copy link
Collaborator Author

Cherry-picked fix to #5573

@cristianoc cristianoc changed the title Branch for release 10.0 [Do Not Merge] Branch for official release 10.0.0 [Do Not Merge] Aug 23, 2022
@cristianoc cristianoc changed the title Branch for official release 10.0.0 [Do Not Merge] Branch for official release 10.0.x [Do Not Merge] Aug 30, 2022
@cristianoc cristianoc changed the title Branch for official release 10.0.x [Do Not Merge] Branch for official releases 10.0.x [Do Not Merge] Aug 30, 2022
@cristianoc
Copy link
Collaborator Author

Now should be ready for 10.0.1.

@cristianoc
Copy link
Collaborator Author

cristianoc commented Sep 5, 2022

@ryyppy could you cherry-pick the last comments commits onto master?
No new 10.0.x release planned unless new issues found.

@cristianoc cristianoc closed this Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

6 participants