-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Tracking issue] Dapr Workflows Stable #8008
Comments
Hello, this keeps happening. #7824 |
@dapr/approvers-dotnet-sdk @dapr/maintainers-dotnet-sdk - Are all of these SDK issues proportionate, necessary, appropriate and is there bandwidth to get them completed for workflows to be stable? |
@mikeee I wasn't clear btw, I fully expect the above list to be triaged for suitability by the maintainers for what is in and out of scope for 1.15 :) |
Thought so, I'll await the dotnet-sdk maintainers to triage the SDK items |
I'll be helping out with the triage of these items over the next few days. |
@olitomlinson I think #3417 might be referring to GitHub actions workflows and not Dapr Workflow. If you agree, then we can probably take it off this list. |
I went ahead and added [P_] next to the above issues for us to better see what work is a P0 for this release |
@cgillum this should probably go on the list too right? (And fixes for all other language SDKS) |
@olitomlinson @cgillum I'll be going through the go, python and javascript SDKs to review the different changes we need pursuing SDK parity and workflows to become stable So far this is a list of issue for the go sdk that I believe should be tracked here:
|
Here are the issues for the python SDK, notice the issues that are closed should be re-opened
|
And the js sdk issues, the durabletask-js issues would need their counterpart issues created in the js-sdk repo:
|
@olitomlinson The top P0 item in the .NET SDK referencing dapr/dotnet-sdk#1344 can be marked off as completed. So can the P0 item referencing an Unknown status referencing dapr/dotnet-sdk#1215 |
Added prioritized list of Java SDK issues to the OP. |
@olitomlinson I'd like to propose adding #7321 to the stabilization list as it's a named issue on the Workflow Limitations, but the issue was closed due to staleness. |
This issue will be the source of truth for collating all tasks what must be complete in order for Workflows to progress to Stable, for the 1.15 release.
Dapr Runtime / durabletask-go
Contrib / State Store
Quickstarts
Perf
Docs
SDKs
.NET SDK
DaprClient
dotnet-sdk#1344Unknown
after being paused using dotnet-sdk#1215Java SDK
String
instead of only class canonical name java-sdk#966Deferred / Not essential for Stable
The text was updated successfully, but these errors were encountered: