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

Generic -Xopt-in support #676

Merged
merged 3 commits into from
Mar 9, 2022
Merged

Conversation

sugarmanz
Copy link
Contributor

@sugarmanz sugarmanz commented Feb 4, 2022

Inspired from conversation on #653 to solve for #603.

I'm only opening this PR because this is a feature I needed today and haven't seen any movement on #653 in almost a month. Feel free to disregard if this PR is redundant pending work from #653.

If necessary, I can add to some of the other opts.bzl files, but it wasn't clear to me the resolution of this comment since the PR was approved afterwards:
#653 (comment)

@restingbull restingbull self-assigned this Mar 4, 2022
@restingbull
Copy link
Collaborator

TODO: Resolve conflicts.

Copy link
Collaborator

@nkoroste nkoroste left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Collaborator

@Bencodes Bencodes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm. Tested this one against our repo as well. Thanks for the PR!

@Bencodes Bencodes merged commit e8f40d5 into bazelbuild:master Mar 9, 2022
@sugarmanz sugarmanz deleted the opt-in-support branch March 28, 2022 19:05
@xaka
Copy link

xaka commented Apr 11, 2022

Is it possible to backport this change to 1.5.x branch and make another release while 1.6 is still in progress?

@brettwooldridge
Copy link
Contributor

I think it would be great to see smaller but more frequent releases. The cadance in the past has been 6mos-1yr between releases. In my opinion, it would be better to have a release every 2-3 months with whatever changes and fixes have been made during that period. In addition to benefiting end-users, I feel like this would also generate more activity on the project itself.

It feels like there are enough improvements in just in the past 2 months to justify a 1.6.0 release.

What do you guys think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants