Skip to content
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

Closed
3 of 4 tasks
MaxDesiatov opened this issue Jun 30, 2020 · 9 comments
Closed
3 of 4 tasks

0.2.0 release #131

MaxDesiatov opened this issue Jun 30, 2020 · 9 comments

Comments

@MaxDesiatov
Copy link
Collaborator

MaxDesiatov commented Jun 30, 2020

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:

  • Basic documentation
    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.
  • Cleaning up the demo example
    I think even without NavigationView and friends, I'll just add some padding and headers to describe what's what
  • Updated CHANGELOG.md
  • Tagging and sharing on Twitter

What are your thoughts @carson-katri @j-f1?

@j-f1

This comment has been minimized.

@MaxDesiatov

This comment has been minimized.

@carson-katri
Copy link
Member

I'm working on getting TokamakDocs to be more stable, but it could be run on a merge if possible...

@MaxDesiatov
Copy link
Collaborator Author

Great idea! I can host it on S3/CloudFront, just need to set up the deployment for it.

@carson-katri
Copy link
Member

The most recent commit should be working with the doc-gen branch.

@carson-katri
Copy link
Member

Should it be 1.0.0 (per Semantic Versioning)?

@MaxDesiatov
Copy link
Collaborator Author

I'd prefer to bump it to 1.0.0 when reach close to 100% API coverage, otherwise we fall under this rule:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

@MaxDesiatov
Copy link
Collaborator Author

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 😄

@MaxDesiatov
Copy link
Collaborator Author

0.2.0 is released, congratulations to everyone involved 👏

We kind of had a circular dependency where new features required a new release of carton, while a new release of carton required some new Tokamak release so that carton init can pull it in its new project template. The demo project is still not very organized, but let's resolve that separately as a part of #130.

I think new releases will follow at much higher frequency now that we're fully out of hiatus 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants