-
Notifications
You must be signed in to change notification settings - Fork 901
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
How to proceed rustfmt 2.0 release #3852
Comments
I had one question,
How long will that be the case? Will minor/bug fix PRs not be accepted until the 2.0 refactoring of the codebase (like #1583 and #3841) is complete, or not until after 2.0 is released, etc. |
At first I thought that it would be ~1 month, but unfortunately, it turns out that I won't be able to devote much time on rustfmt in the next few months. As such, I will relax the restriction and accept any PRs to the master branch. Backporting to 1.4.z will not likely to happen, though. |
@topecongiro - do we have a means today within rustup to provide an opt-in version of the rustfmt 2.0 release candidate (once we are ready) on nightly, or will rustfmt on nightly immediately transition from rustfmt 1.4.15 to rustfmt 2.0 once we update the submod? Just trying to think through the impact that'll occur once we have 2.0 ready, especially for those folks building on nightly and running rustfmt as part of their CI since there will be a lot of formatting changes. |
It has been more than a year since the release of the rustfmt 1.0, and it's high time to prepare for the next major version update 🎉
I am thinking of moving things forward in the following way. Any thoughts on improvement or questions?
After the next patch release (1.4.10), the master branch will be a development branch for the rustfmt 2.0. We will accept PRs to the master branch only if they belong to the 2.0 milestone. We will NOT accept PRs that fixes minor bug fixes. If there are critical bugs that we need to fix as soon as possible (e.g., the breaking changes from the rustc internal that requires updating
rustc-ap-*
crates), then we will create a branch for the 1.4.11.We will start with removing version gates and separating rustfmt into multiple crates.
The text was updated successfully, but these errors were encountered: