Closed J17359 closed 1 year ago
Would you be able to test the pre-release of version 2.2.0? We are currently doing some basic testing but would like you to test this draft release to make sure everything looks good before making it official.
https://github.com/ZeligsoftDev/CX4CBDDS/releases/tag/v2.2.0-RC1
Would you be able to test the pre-release of version 2.2.0? We are currently doing some basic testing but would like you to test this draft release to make sure everything looks good before making it official.
https://github.com/ZeligsoftDev/CX4CBDDS/releases/tag/v2.2.0-RC1
I'm building the RPM internally and then will have @j26151 perform a sanity check on it when he gets online. Will post back here afterwards!
I just briefly tested generated descriptors and IDL on a more complicated model of ours without seeing any issues. I also tested the new text editor change (removing RTF as default) and that worked as well.
@ysroh is there anything else you need us to verify before making the official tag?
Thanks for verifying the build. We will create an official v2.2.0 tag today and let you know.
I see the new tag now. Let me know once you've rolled the papyrus
branch to the new version so we can ensure our latest 2.2.0 version matches your latest hash internally. Thanks again!
Release 2.2.0 is created: https://github.com/ZeligsoftDev/CX4CBDDS/releases/tag/v2.2.0 I will bump versions on papyrus branch next, then create the 2.2.x maintenance branch and bump versions there.
@J17359 : pull requests for a version bumped 2.3.0 papyrus branch and 2.2.1 v2.2.x-maintenance branch are above. The attached build artifacts should all be correctly versions. Have a quick look yourself to confirm and let me know.
@elder4p PRs look good to me! Thanks for the quick turnaround on this one!
@elder4p - actually, look at the 2.2.X PR for me. It might be missing changes in 2 files...
@elder4p - actually, look at the 2.2.X PR for me. It might be missing changes in 2 files...
@J17359 : Good catch. Missed two files related to the v4.4.0 patch. Technically, not used any more, but if it's in the repo, it should build. Update coming shortly.
@elder4p - Looks good now!
PRs #436 and #437 have been merged. Closing.
Issue and tracking information
Developer's time Estimated effort to fix (hours):
Developer's Actual time spent on fix (hours)
Issue reporter to provide a detailed description of the issue in the space below
Could you please perform the following release steps in addition to any of your own?
papyrus
branch for the 2.2.0 releasepapyrus
branch to create a newstreams/v2.2.x-maintenance
branchpapyrus
branch to 2.3.0streams/v2.2.x-maintenance
branch to 2.2.1Thanks! Please let @j26151 or I know if there are any questions/concerns.