Rust SDK 4.0 stabilization tracker

[austinabell]

Probably a good idea to keep track of things we want to be sure of before the 4.0 release:

• [x] fix: private annotation codegen to include near_sdk prefix #491
• [x] feat(env): Replace panic with panic_str and add abort method #492
• [x] Borsh to 0.9, which would require releases of VM logic crates (to avoid duplicate deps for tests) chore: remove lockfile, bump versions #476 Address unit tests using old nearcore version #500 Upgrade to borsh 0.9 nearcore#4603 chore: update borsh and nearcore crate versions in SDK #639
• [x] Resolution on chained promises with nesting are executed out of order #263 so this doesn't keep getting pushed back?
• [x] Switch storage keys to Box<<span class="error">[u8]</span>>?
• [x] refactor(env)!: remove public key generics from promise API #495
• [x] fix: mock sys interface panic signature #497
• [x] PublicKey type ignores validation on deserialization #498
• [x] Resolution on Delay scheduling batch promises until end of method invocation #526 (API will be changed for next major release)
• [x] refactor: remove rust panic calls from examples and SDK code #527
• [x] fix: method parameter to string from bytes for promise and receipts #521
• [x] fix: metadata codegen warning #520
• [x] chore: Add MIT and Apache licenses and update crate licenses nearcore#4732 (license updates, remove gpl3 requirement from SDK)
• [x] Implement NEP264 host function and refactor ext contract API #740 feat: refactor ext API and add new NEP264 functionality #742
• [x] Update nearcore crates to include new function call weight #813
• [x] Remove sim codegen from near_bindgen #802 chore: remove near-sdk-sim from repo #817

Feel free to add anything else relevant or thoughts on these!

[robert-zaremba]

Any ETA for the release?

[austinabell]

Any ETA for the release?

Hard to give a good estimate for ETA, as is it dependant on a few things out of our control. Will try to update here when we have a better idea.

[jberrytech]

Sprint planning update: Awaiting resolution for NEP. @austinabell will provide more detail.

[jberrytech]

@jberrytech organizing a formal tech review.