Hi there, On behalf of CRS QE and Fuse Tooling QE be aware that CR Studio 12.21.1.GA and JBT 4.21.1.Final were tested and approved. JBoss Tools 4.21.1.Final and CodeReady Studio 12.21.1.GA are ready to be released [1]. There are still some critical issues (you can find them in the sign-off document below). These issues do not block the GA release, however as we move towards the next release they could be considered as blockers. The sign-off document is here: https://source.redhat.com/groups/public/jbds-qe/jbds_qe_wiki/qe_sign_off_... Thanks, CRS QE team. Ondrej P.S. Many thanks to all involved folks. Please also take a look at sign off document so we can correct any errors. [1]: https://issues.redhat.com/browse/SPMM-8230

Hello, JBoss Tools 4.21.2.Final and CodeReady Studio 12.21.2.GA are ready to be released. There are still some critical issues (you can find them in the sign-off document below). These issues do not block the GA release, however as we move towards the next release they could be considered as blockers. The sign-off document can be found here [1]. Thanks, On behalf of CRS QE and Fuse Tooling QE Ondrej Dockal CodeReady Studio QE lead [1]: https://source.redhat.com/groups/public/jbds-qe/jbds_qe_wiki/qe_sign_off_...

Hello, As indicated previously, we extended the code freeze until today due to some major changes in the jbosstools github repositories. in short, we changed the default branch from 'master' to 'main'. ( see https://issues.redhat.com/browse/JBIDE-28036 ) This move is now complete. All the active jbosstools and jbdevstudio repositories are using 'main' branch as default. On GitHub side, the migration automatically took care of open prs, draft, rules and also takes care of redirecting users to the correct branch ( https://github.com/github/renaming ) On your side, depending on how you configured your remote, you *may* have errors when fetching the repository. there are two options : - fetching will automatically change the remote tracked branch from master to main. - fetching will fail with an error saying the remote branch cannot be resolved. if you experience the second case scenario, here are the steps to perform in the corresponding directory to switch the remote config : In all cases, if you had a local 'master' branch, it will remain named like it, but the remote-tracking branch should be changed to origin/main. CI and GitHub actions were also patched. If you experience any issues, please let us know. This also ends the code freeze, all main branches are now open for PRs. Regards, Le mer. 2 févr. 2022 à 11:51, Ondrej Dockal <odockal(a)redhat.com&gt; a écrit : -- Stéphane Bouchet Senior Software Engineer, R&D Red Hat <https://www.redhat.com/> <https://www.redhat.com/>