Skip to content
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

Status of Bazel 5.0.0-pre.20210604.6 #13572

Closed
6 tasks done
fweikert opened this issue Jun 11, 2021 · 7 comments
Closed
6 tasks done

Status of Bazel 5.0.0-pre.20210604.6 #13572

fweikert opened this issue Jun 11, 2021 · 7 comments
Assignees
Labels
P1 I'll work on this now. (Assignee required) release team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: process

Comments

@fweikert
Copy link
Member

fweikert commented Jun 11, 2021

  • Expected release date: June 11th

Task list:

@fweikert fweikert added P1 I'll work on this now. (Assignee required) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website release type: process labels Jun 11, 2021
@fweikert
Copy link
Member Author

cc @konste: This release contains 2f0927a

@konste
Copy link

konste commented Jun 11, 2021

@fweikert Thank you for letting me know! This is great, we are waiting for 2f0927a.

But frankly we are very confused about multiple release "trains" going on at the same time. Between this and 4.2.0 which is expected to release earlier? Is this 5.0.0 or some pre-release of 5.0.0? Where are rolling releases in this picture?

@konste
Copy link

konste commented Jun 11, 2021

Also we tested 5.0.0-pre.20210510.2.2 and found that it removed the flag --noincompatible_blacklisted_protos_requires_proto_info which we still rely on. Is it possible to revert it? I am trying to dig more details now.

@brentleyjones
Copy link
Contributor

brentleyjones commented Jun 11, 2021

Is this 5.0.0 or some pre-release of 5.0.0?

This is the development branch, which will eventually be branched to 5.0.0 in September. 4.2.0 is based on the 4.1.0 branch, which is based on the 4.0.0 branch, and only contains cherry-picks, while these releases are branches regularly from master.

https://docs.bazel.build/versions/main/versioning.html covers the difference. 4.2.0 is a minor release of the Bazel 4 LTS release. This is a rolling release.

@fweikert
Copy link
Member Author

fweikert commented Jun 11, 2021

Going forward we're offering two parallel release trains instead of the old "one release a month" train:

  • LTS releases: These are stable releases that have been tested thoroughly and will be released less frequently. A new major release happens roughly every nine months (starting with 4.0.0). We'll provide minor patch releases if bug/security fixes are necessary.
  • Rolling releases: These are released much more frequently (typically weekly), but at the cost of stability. They're for early adopters who want to try new features, but don't want to wait for the next major LTS release (5.0.0 in this case).

The official announcement can be found here: https://blog.bazel.build/2020/11/10/long-term-support-release.html

@konste
Copy link

konste commented Jun 11, 2021

Thank you @brentleyjones and @fweikert for clarification. I was aware of LTS vs Rolling plan, but it was not obvious that 5.0.0-pre IS the Rolling train. Now it makes sense.

@fweikert
Copy link
Member Author

fweikert commented Jun 11, 2021

Yes, you'll see many more 5.0.0-pre... rolling releases until we release 5.0.0 LTS, then all rolling releases will be named 6.0.0-pre...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 I'll work on this now. (Assignee required) release team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: process
Projects
None yet
Development

No branches or pull requests

3 participants