2019-01-25 12:41:43 -05:00
|
|
|
# Roadmap for neo-go
|
|
|
|
|
|
2019-09-18 12:06:10 +03:00
|
|
|
This defines approximate plan of neo-go releases and key features planned for
|
2022-04-20 21:30:09 +03:00
|
|
|
them. Things can change if there is a need to push a bugfix or some critical
|
2019-10-25 18:30:17 +03:00
|
|
|
functionality.
|
2019-09-18 12:06:10 +03:00
|
|
|
|
2020-02-06 21:35:43 +03:00
|
|
|
## Versions 0.7X.Y (as needed)
|
|
|
|
|
* Neo 2.0 support (bug fixes, minor functionality additions)
|
|
|
|
|
|
2025-02-11 17:07:46 +03:00
|
|
|
## Version 0.109.0 (~April 2025)
|
2023-12-29 16:19:48 +03:00
|
|
|
* protocol updates
|
2024-05-21 12:51:33 +03:00
|
|
|
* bug fixes
|
2025-02-11 17:07:46 +03:00
|
|
|
* NeoFS-based synchronization
|
2022-11-10 16:18:59 +03:00
|
|
|
|
2023-12-29 16:19:48 +03:00
|
|
|
## Version 1.0 (2024, TBD)
|
2022-11-10 16:18:59 +03: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.
|
|
|
|
|
|
