-
-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.2.0 release #131
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I'm working on getting TokamakDocs to be more stable, but it could be run on a merge if possible... |
Great idea! I can host it on S3/CloudFront, just need to set up the deployment for it. |
The most recent commit should be working with the |
Should it be |
I'd prefer to bump it to
|
Especially if we tag the release before the Xcode 12 GM is out (which I hope we do), some of the new APIs could change by then. Using 0.y.z is safe from that perspective 😄 |
0.2.0 is released, congratulations to everyone involved 👏 We kind of had a circular dependency where new features required a new release of I think new releases will follow at much higher frequency now that we're fully out of hiatus 😄 |
Just kickstarting a possible discussion here of what you'd like to see in the first release with the SwiftUI API subset supporting WebAssembly. I am personally a fan of "release early and often" idea and wouldn't mind tagging a release with whatever API coverage we already have. It's more about letting people know that this thing exists and it can do basic stuff.
These seem to be release blockers, let me know if you think anything's missing:
The existing
progress.md
should be enough for this first release, I guess? We can integrate TokamakDocs somehow in later versions, unless @carson-katri has any objections.I think even without
NavigationView
and friends, I'll just add some padding and headers to describe what's whatWhat are your thoughts @carson-katri @j-f1?
The text was updated successfully, but these errors were encountered: