Functions v4 Breaking Change Process #1909
brettsam
announced in
Design discussions
Replies: 5 comments
-
I cannot select discussion category which blocks me from creating a new discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
-
Yeah, I think Brett already created one for me. Thanks Fabio. #1967 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
With Functions v4 (running on .NET 6.0), we want to take a very deliberate approach to breaking changes. We're requiring that all potential changes are proposed and approved. We've also created a template to guide these proposals and ensure that most scenarios are considered before presenting.
It is not a goal that a customer can change their site extension version from ~3 to ~4 and be guaranteed to run without errors. However, we want to have as smooth as an upgrade path as possible. This includes:
AllowSynchronousIO
feature flag, it will be enabled again.Breaking changes will not be accepted after some future date (TBD), to allow for stabilization before GA.
Breaking Change Approval Process
The approval process looks like:
All discussions for a proposal will happen in github disscussions and only updates/approvals/etc will be made in the original issue. This allows for customers to follow the issue without getting notified of every reply to the discussion.
Design discussions
.Beta Was this translation helpful? Give feedback.
All reactions