Skip to content
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.0.0 Checklist #2519

Closed
24 tasks done
superboyiii opened this issue Jul 2, 2021 · 10 comments
Closed
24 tasks done

Neo v3.0.0 Checklist #2519

superboyiii opened this issue Jul 2, 2021 · 10 comments
Labels
Discussion Initial issue state - proposed but not yet accepted

Comments

@superboyiii
Copy link
Member

superboyiii commented Jul 2, 2021

Now We're making the checklist of neo v3.0.0 for release preparation. We plan to release v3.0.0 in the middle of July and then testnet will be launched. There will be a data reset on v3.0.0 testnet and then no reset any more. We plan to run Testnet for several weeks to ensure it's stable enough and then Mainnet will be launched. Most of the PRs on this checklist has been solved or nearly to be merged. Additional tasks collection will be accepted only if it's necessary.

Mandatory issues

Mandatory PRs

@neo-project/developers @neo-project/core @neo-project/ngd-seattle

@superboyiii superboyiii added the Discussion Initial issue state - proposed but not yet accepted label Jul 2, 2021
@csmuller
Copy link

csmuller commented Jul 2, 2021

@superboyiii, PR #2497 is only a partial fix to the issues with calculatenetworkfee. What about #2501?

@superboyiii
Copy link
Member Author

@superboyiii, PR #2497 is only a partial fix to the issues with calculatenetworkfee. What about #2501?

We'll push a PR to fix it soon. Added to checklist.

@devhawk
Copy link
Contributor

devhawk commented Jul 2, 2021

Runtime.Network (i.e. #2515) also needs to be added to devpack. Probably can be done as part of neo-project/neo-devpack-dotnet#648

@devhawk
Copy link
Contributor

devhawk commented Jul 2, 2021

Final decision about #2425 should be on this list

@superboyiii
Copy link
Member Author

superboyiii commented Jul 5, 2021

Final decision about #2425 should be on this list

We plan to implement current neo-go solution when mainnet launched. C# version need more time to test for details.
PS: We plan to make multi-sig by smart contract in C# version instead of Notary.

@roman-khimov
Copy link
Contributor

roman-khimov commented Jul 13, 2021

#2536, #2534, neo-project/neo-vm#418 seem to be release-critical to me. Worth considering: neo-project/neo-vm#421 (it's hard to change it afterwards).

@superboyiii
Copy link
Member Author

#2536, #2534, neo-project/neo-vm#418 seem to be release-critical to me. Worth considering: neo-project/neo-vm#421 (it's hard to change it afterwards).

All added

@roman-khimov
Copy link
Contributor

Please also add #2541, current Murmur implementation is non-standard which will lead to interoperability issues between various node implementations.

@ioannistsil
Copy link

@superboyiii all merged update checklist please :)

@superboyiii
Copy link
Member Author

Mainnet launched. Neo to the moon! 🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Initial issue state - proposed but not yet accepted
Projects
None yet
Development

No branches or pull requests

5 participants