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
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 (
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
- fetching will fail with an error saying the remote branch cannot be
if you experience the second case scenario, here are the steps to perform
in the corresponding directory to switch the remote config :
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
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.
Le mer. 2 févr. 2022 à 11:51, Ondrej Dockal <odockal(a)redhat.com> a écrit :
JBoss Tools 4.21.3.Final and CodeReady Studio 12.21.3.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 .
The master branch is *STILL* frozen. Due to required work on repos and
infra we are not removing code freeze. Please *DO NOT MERGE* anything
unless we (with Stephane) will notify you when we are done. Thank you!
On behalf of CRS QE and Fuse Tooling QE
CodeReady Studio QE lead
Senior Software Engineer, R&D
Red Hat <https://www.redhat.com/>