2019-01-25 17:41:43 +00:00
|
|
|
# Roadmap for neo-go
|
|
|
|
|
|
2019-09-18 09:06:10 +00:00
|
|
|
This defines approximate plan of neo-go releases and key features planned for
|
2022-04-20 18:30:09 +00:00
|
|
|
them. Things can change if there is a need to push a bugfix or some critical
|
2019-10-25 15:30:17 +00:00
|
|
|
functionality.
|
2019-09-18 09:06:10 +00:00
|
|
|
|
2020-02-06 18:35:43 +00:00
|
|
|
## Versions 0.7X.Y (as needed)
|
|
|
|
|
* Neo 2.0 support (bug fixes, minor functionality additions)
|
|
|
|
|
|
2024-11-29 16:55:22 +00:00
|
|
|
## Version 0.108.0 (~Jan-Feb 2025)
|
2023-12-29 13:19:48 +00:00
|
|
|
* protocol updates
|
2024-05-21 09:51:33 +00:00
|
|
|
* bug fixes
|
|
|
|
|
* node resynchronisation from local DB
|
2022-11-10 13:18:59 +00:00
|
|
|
|
2023-12-29 13:19:48 +00:00
|
|
|
## Version 1.0 (2024, TBD)
|
2022-11-10 13:18:59 +00:00
|
|
|
* stable version
|
|
|
|
|
|
|
|
|
|
# Deprecated functionality
|
|
|
|
|
|
|
|
|
|
As the node and the protocol evolve some external APIs can change. Usually we
|
|
|
|
|
try keeping backwards compatibility for some time (like half a year) unless
|
|
|
|
|
it's impossible to do for some reason. But eventually old
|
|
|
|
|
APIs/commands/configurations will be removed and here is a list of scheduled
|
|
|
|
|
breaking changes. Consider changing your code/scripts/configurations if you're
|
|
|
|
|
using anything mentioned here.
|
|
|
|
|
|
2024-11-15 10:05:42 +00:00
|
|
|
## Dump*Slot() methods of `vm.Context`
|
|
|
|
|
|
|
|
|
|
The following new methods have been exposed to give access to VM context slot contents
|
|
|
|
|
with greater flexibility:
|
|
|
|
|
- `ArgumentsSlot`
|
|
|
|
|
- `LocalsSlot`
|
|
|
|
|
- `StaticsSlot`.
|
|
|
|
|
|
2024-11-19 19:23:05 +00:00
|
|
|
Removal of the `Dump*Slot()` methods are scheduled for the 0.108.0 release.
|
