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.6.2 plan #2914

Closed
roman-khimov opened this issue Sep 18, 2023 · 19 comments
Closed

Neo v3.6.2 plan #2914

roman-khimov opened this issue Sep 18, 2023 · 19 comments
Labels
critical Issues (bugs) that need to be fixed ASAP plan Plan for the next version

Comments

@roman-khimov
Copy link
Contributor

roman-khimov commented Sep 18, 2023

Summary or problem description
We have a number of known issues that need to be addressed before rolling 3.6 into mainnet (and to have properly functioning testnet). #2910 only has a part of the problem and we need some place to track all the other ones.
3.6 is running on the mainnet, but it has a number of issues that better be fixed soon.

Do you have any solution you want to propose?
We need a 3.6.1 and I'd say we need it this week. master currently contains additional changes from #2905, but we need to concentrate on stabilizing the set we have in 3.6.0, so the proposal is to merge the respective PRs into master (as they're now), then branch off of 4e9314d (and corresponding v3.6.0 commits elsewhere, like in modules) and cherry-pick required changes there.

Modules 3.6.1
Since neo-project/neo-modules#829 has affected users seriously, neo-modules 3.6.1 were released without corresponding core/cli releases, this version has fixed:

v3.6.2
Given the modules situtation, the next release for every component should be 3.6.2.

Mandatory issues to fix:

Discussion:

Related PRs:

Suggestions/opinions/alternatives are welcome. I'll add some comments below to keep these lists clean.

@roman-khimov roman-khimov added the discussion Initial issue state - proposed but not yet accepted label Sep 18, 2023
@roman-khimov
Copy link
Contributor Author

The "mandatory" list above is as conservative as it could be, following the "have resynchronization fun" paradigm. It's not final and my proposal is to extend it with:

@roman-khimov roman-khimov changed the title Neo 3.6.1 plan Neo v3.6.1 plan Sep 18, 2023
@steven1227
Copy link
Member

Fully agree on this one.

@roman-khimov
Copy link
Contributor Author

Mainnet is at 3.6 now, which makes 3.6-specific part of #2910 irrelevant (not the underlying problem, of course), removed from the list.

@roman-khimov
Copy link
Contributor Author

Retracting #2894 (unsafe wrt state change, not worth any delay). Let's at least push the main set out the door.

@roman-khimov
Copy link
Contributor Author

@roman-khimov roman-khimov changed the title Neo v3.6.1 plan Neo v3.6.2 plan Sep 25, 2023
@roman-khimov
Copy link
Contributor Author

@shargon
Copy link
Member

shargon commented Sep 27, 2023

Added #2920

@superboyiii
Copy link
Member

neo-project/neo-node#903, Please

@AnnaShaleva
Copy link
Member

Let's consider the neo-project/neo-modules#838, please. It's related to neo-project/neo-modules#822.

@roman-khimov
Copy link
Contributor Author

Added neo-project/neo-vm#514, can be replaced if doesn't fit for some reason, but the issue needs to be fixed.

@Jim8y Jim8y added the plan Plan for the next version label Oct 19, 2023
@Jim8y Jim8y pinned this issue Oct 19, 2023
@AnnaShaleva
Copy link
Member

#2939 should also be added.

@roman-khimov
Copy link
Contributor Author

#2939 should also be added.

Sure.

@shargon
Copy link
Member

shargon commented Nov 7, 2023

#2942 should be added in 3.6 2

@roman-khimov
Copy link
Contributor Author

But why? We can deliver the set of changes from the list in a patch release and then deal with these extensions. The idea was to have a quick release fixing the most critical problems. Otherwise I'd say 3.6.2 is in trouble, we're risking destabilizing it with too many changes.

@shargon
Copy link
Member

shargon commented Nov 7, 2023

But why? We can deliver the set of changes from the list in a patch release and then deal with these extensions. The idea was to have a quick release fixing the most critical problems. Otherwise I'd say 3.6.2 is in trouble, we're risking destabilizing it with too many changes.

We currently merged some changes that affects hardforks with native contracts, but agree that currently are not used, so we can focus on this, and prioritize it for the next release.

@shargon shargon added critical Issues (bugs) that need to be fixed ASAP and removed discussion Initial issue state - proposed but not yet accepted labels Nov 7, 2023
@shargon
Copy link
Member

shargon commented Nov 10, 2023

@superboyiii Ready to fly

@Jim8y
Copy link
Contributor

Jim8y commented Nov 16, 2023

Propose to close this issue since version 3.6.2 is released.

@shargon
Copy link
Member

shargon commented Nov 16, 2023

Released 3.6.2

@shargon shargon closed this as completed Nov 16, 2023
@roman-khimov
Copy link
Contributor Author

Huh. I'd do it after I see something in https://github.com/neo-project/neo-node/releases, but OK and it'll be easier with #2944.

@roman-khimov roman-khimov unpinned this issue Nov 16, 2023
@mialbu mialbu mentioned this issue Nov 30, 2023
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical Issues (bugs) that need to be fixed ASAP plan Plan for the next version
Projects
None yet
Development

No branches or pull requests

6 participants