No problem for me. I'm OK skipping the deprecation path. I don't see it as necessary, I was simply trying to accommodate other opinions. I have created a second PR which is identical to the first, but without the deprecation warning [4].
Also in the review Tim suggested the following:
I wonder if template-based widget rendering (#15667) might ease this change. A project could provide custom widget templates if they don't want the required attribute (or if they want required='required'.
This is a different approach than previously discussed. I see the merit in this suggestion and think it could be a better implementation. With this idea, we could avoid adding the Form.use_required_attribute, entirely. However, template-based widget is still very much a WIP. I worry waiting on that feature may mean this simpler feature may miss a release cycle. Is it reasonable to expect the template-based widget rendering to land before the next alpha/beta cut?
Tim asked I post these ideas to the mailing to get other opinions and feedback on these two points.
Thanks,
Jon