Skip to content
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.

Update hello-world.mdx #676

Closed
wants to merge 1 commit into from

Conversation

waldmatias
Copy link
Contributor

Updated sdk to 20.0.0
Updated soroban-cli to 20.0.1

Updated sdk to 20.0.0
@ElliotFriend
Copy link
Contributor

This is a bit of a tricky one, perhaps. Futurenet requires v20.0.1, but Testnet (I'm pretty sure) will only work with v20.0.0-rc2.2 until it resets on the 18th... I even started #671 to make sure we're compatible with Testnet (not yet merge, tho).

Not sure which direction we should go. I'd hate to add notes everywhere that say "use version x for futurenet and version y for testnet." That lends itself to forgetting to update/remove them when the time comes. I don't really want to just ignore one or the other, either... 🤔

Any thoughts or suggestions?

@ElliotFriend
Copy link
Contributor

I think we have tended to generally favor testnet as the "default" or "typical" network in the docs up to this point, though. So, maybe we try to stick to that?? Doesn't feel like a great answer, to be honest hehehe

@waldmatias
Copy link
Contributor Author

waldmatias commented Dec 8, 2023

Well ... if something is breaking today between futurenet and testnet that results in a dev needing to use different sdk versions, that should be documented (so you can keep the 'default' as applying to testnet requirements, but there should be a note below that says 'if you are using futurenet, you'll need to switch to using v.XXX'). I mean, I know it is hard to sync, but reading the docs is what you should be doing first, right? 😆 How would I know which sdk I need to use for different networks, and in that sense, it is most likely that if I'm reading a "hello world" I would actualy might end up deploying first to futurenet, no?
But then again, the next step is called deploy to testnet, so perhaps futurenet is out.

Do we want everyone deploying to testnet and not futurenet?

@ElliotFriend
Copy link
Contributor

Do we want everyone deploying to testnet and not futurenet?

Generally speaking, that's the direction the docs lean. I don't think it's really spelled out clearly anywhere, but there are certain pros/cons to each. It seems that Testnet is preferred, and how (or if) futurenet is used in the future is a bit up-in-the air at this point.

I think since we're typically using Testnet in the docs, it makes sense to leave the rc versions of the SDKs for now? Maybe anywhere that specifically uses Futurenet (dapps challenges maybe?) we should add a note to change SDK versions for now?

@waldmatias
Copy link
Contributor Author

Given we're theoretically just waiting for a reset on the 18th (and everything should sync up, both sdk and cli) then I guess it is fine to leave rc versions. In any case, we've left some insight in these comments for anyone having a problem until then with versioning 😄

@ElliotFriend
Copy link
Contributor

@waldmatias Looks like this is officially unnecessary now lol. Thanks for the contribution and insightful conversation!

@waldmatias waldmatias deleted the patch-4 branch March 13, 2024 22:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants