You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every time a new release appears on the oura repository, we have to look at each change, then look at upcoming hard forks on cardano-node and make sure that:
The new post-hardfork-supporting cardano-node is supported by the new oura version.
The new oura version is required for the hardfork. (ie. can we just upgrade the cardano-node without re-compiling the Rust binary that uses oura)
It would be nice to know: "ok, to prepare for the hardfork we need to upgrade cardano-node to X and oura to Y. Good." or "ok, all we need to upgrade is cardano-node, oura should work as-is" instead of every time reading the source code and seeing if it lines up with the breaking changes added to the hardfork on the cardano-node side.
The text was updated successfully, but these errors were encountered:
Every time a new release appears on the oura repository, we have to look at each change, then look at upcoming hard forks on cardano-node and make sure that:
It would be nice to know: "ok, to prepare for the hardfork we need to upgrade cardano-node to X and oura to Y. Good." or "ok, all we need to upgrade is cardano-node, oura should work as-is" instead of every time reading the source code and seeing if it lines up with the breaking changes added to the hardfork on the cardano-node side.
The text was updated successfully, but these errors were encountered: