Skip to content

[EPIC] Transaction Support Issues and Pull Requests #1339

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

Open
14 tasks
jonathanc-n opened this issue May 16, 2025 · 2 comments
Open
14 tasks

[EPIC] Transaction Support Issues and Pull Requests #1339

jonathanc-n opened this issue May 16, 2025 · 2 comments
Labels
epic Epic issue

Comments

@jonathanc-n
Copy link
Contributor

jonathanc-n commented May 16, 2025

What's the feature are you trying to implement?

There is an accumulation of issues + PRs related to transactions which has made it quite difficult to follow on to the transaction support progress (there are duplicate pull requests, issues, etc. being made ). This is a list to help new contributors be aware of what is being worked on + reviewers have a easy place to access pull requests that can be looked at 😄:

Issues (without pull request)

Pull Requests 🚀

I have listed out some issues that are dependant on other pull requests. I will be maintaining this as issues + pull requests are being made, feel free to let me know if I need to add something!

@jonathanc-n jonathanc-n added the epic Epic issue label May 16, 2025
@Xuanwo
Copy link
Member

Xuanwo commented May 16, 2025

Thank you @jonathanc-n for gathering this information. I’ll begin reviewing the pending PRs.

@liurenjie1024
Copy link
Contributor

Thanks @jonathanc-n for this summary. Transaction support is a somewhat large topic. Except reviewing prs, we also need to have a design to split it into smaller issues, so that the community could make progress on it. I'm do the planning recently.

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

No branches or pull requests

3 participants