CHANGELOG: mention Windows!

This commit is contained in:
Roman Khimov 2022-03-21 16:20:19 +03:00
parent 66f5ae8fd9
commit abb19014e1

View file

@ -5,16 +5,17 @@ This document outlines major changes between releases.
## 0.98.2 "Karstification" (21 Mar 2022) ## 0.98.2 "Karstification" (21 Mar 2022)
We've decided to release one more 3.1.0-compatible version bringing all of the We've decided to release one more 3.1.0-compatible version bringing all of the
new features and bug fixes made before going into full 3.2.0 compatibility. new features and bug fixes (along with complete support for Windows platform)
It's important for us to give you more stable and flexible environment for the made before going into full 3.2.0 compatibility. It's important for us to give
ongoing hackathon. Contract bindings generator might be very useful for anyone you more stable and flexible environment for the ongoing hackathon. Contract
operating with already deployed contracts written in other languages, while bindings generator might be very useful for anyone operating with already
the node itself can now be configured for lightweight operation, keeping only deployed contracts written in other languages, while the node itself can now
the data relevant for the past MaxTraceableBlocks, no more and no be configured for lightweight operation, keeping only the data relevant for
less. Current public networks don't benefit from it yet with their large the past MaxTraceableBlocks, no more and no less. Current public networks
MaxTraceableBlocks setting, but they're growing every day and it's just a don't benefit from it yet with their large MaxTraceableBlocks setting, but
matter of time when this feature will start making a difference. And sorry, they're growing every day and it's just a matter of time when this feature
but this release is again faster than the previous one. will start making a difference. And sorry, but this release is again faster
than the previous one.
We recommend updating, but if your node is not public and you don't We recommend updating, but if your node is not public and you don't
specifically want to play with new things brought by it you might as well wait specifically want to play with new things brought by it you might as well wait