-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Neo v3.2.1 Checklist #2676
Comments
Is #2628 also a part of the release? |
Yes, these already merged will be included in the release. |
@superboyiii What's the timeframe on releasing 3.2? I have been letting neo-project/neo-modules#687 languish, but can get it ready by middle of next week for inclusion in 3.2. Would enable a set of new features we want to bring to Neo.Express. But I don't think we should hold up the release for neo-project/neo-modules#687. |
Enough time left. We wish in 2 weeks. |
I realize it is coming in late, but I would really like #2679 to be considered for 3.2. Also, neo-project/neo-modules#687 is just waiting on review. Can we add that to the 3.2 list? |
I hadn't noticed before that neo-modules repo has https://github.com/neo-project/neo-modules/branches |
|
neo-project/neo-modules#698? Or is it considered as a part of #2666? |
No time left for this, can be included in next releae. |
Finally, we will wait for it to be merged into v3.2.1. |
When is https://github.com/neo-project/neo-devpack-dotnet going to be updated to neo 3.2.1? |
Wait for neo-project/neo-devpack-dotnet#731 |
Now We're making the checklist of neo v3.2.1 for release preparation. We plan to release v3.2.1 and then upgrade testnet and mainnet. It's an enhancement version including native contract upgrade, these core issues and PRs are included.
Mandatory issues
Mandatory PRs
Versioned Abi #2632(need better solution)murmur32
to crypto lib #2604@neo-project/core @neo-project/developers @neo-project/ngd-seattle
The text was updated successfully, but these errors were encountered: