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

New Releases? #1166

Open
zamderax opened this issue Oct 20, 2024 · 2 comments
Open

New Releases? #1166

zamderax opened this issue Oct 20, 2024 · 2 comments
Labels
1 - triaged Ticket makes sense and is well defined, ready to be worked on question Further information is requested

Comments

@zamderax
Copy link

I'm so excited about this project and so tempted to get started since it's so close to a 1.0.0 release.

I saw in the README.md this quote:

We anticipate to release a number of 1.0.0-beta-n releases during the beta phase of Swift 5.7, before releasing a source stable 1.0 soon after.

But the latest tagged release is 1.0.0-beta.3 released on Oct 27, 2022

Are there any upcoming releases planned or more frequent releases scheduled. I looked in the Swift forums but couldn't tell. Thank you!

@akbashev
Copy link
Contributor

@zamderax There is no release schedule or something like that, but it doesn't mean it's abandoned. From my POV a lot of effort went into finishing concurrency and language support/improvements of distributed in Swift itself.
Actually I think it's good in a way—we're free to break and improve stuff now, including migration to Swift 6. And anyone can participate.

@ktoso can bring more light here 🙂

@ktoso
Copy link
Member

ktoso commented Oct 24, 2024

In practice we're at this point not rushing to 1.0 anymore. Given that the language feature keeps evolving we'd probably be able to make some quite nicer today with resolvable protocols etc.

If anyone "needs" a release we can just keep cutting beta releases.

For the time being I don't foresee an 1.0 very soon, but the library should be perfectly usable as is.

It's a bit of a chicken and egg problem. I think if we'd polish up to Swift 6.0 and have all the worker pool, discovery etc on distributed actors rather than on behaviors I'd be ok to call a 1.0 at that point.

@ktoso ktoso added question Further information is requested 1 - triaged Ticket makes sense and is well defined, ready to be worked on labels Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - triaged Ticket makes sense and is well defined, ready to be worked on question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants