You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have several companies using Connect-Swift in production at scale
Gather more feedback from the community on Connect's usability and APIs so that we can keep them backward-compatible once v1.0 is reached
At this time, our goal is to tag a v1.0 around July 1, 2024. This timeline will allow us to scale adoption, gather feedback, and react to any big news coming out of WWDC with the goal of minimizing the risk of needing to introduce breaking changes shortly after tagging a v1.0. We plan to tag release candidates in the months leading up to this date.
In the meantime, we encourage the community to stay up-to-date with the latest Connect-Swift version and to share feedback through GitHub issues so that we can improve the library over the coming months before tagging a stable release.
We'll to keep this issue updated as we make progress! 🚀
The text was updated successfully, but these errors were encountered:
This PR includes updates to fix all outstanding conformance test
failures and removes the corresponding opt-outs. All changes are
validated by the conformance test suite.
Many of these fixes are similar to
connectrpc/connect-kotlin#248 and
connectrpc/connect-kotlin#274.
Resolves#268.
Resolves#269.
Resolves#270.
This should also be one of the final changes before v1.0
#222.
---------
Signed-off-by: Michael Rebello <me@michaelrebello.com>
This issue is to track our progress towards tagging a stable v1.0 release of Connect-Swift.
At this time, we've mostly completed the key tasks that we see as prerequisites for a v1.0:
At this time, our goal is to tag a v1.0 around July 1, 2024. This timeline will allow us to scale adoption, gather feedback, and react to any big news coming out of WWDC with the goal of minimizing the risk of needing to introduce breaking changes shortly after tagging a v1.0. We plan to tag release candidates in the months leading up to this date.
In the meantime, we encourage the community to stay up-to-date with the latest Connect-Swift version and to share feedback through GitHub issues so that we can improve the library over the coming months before tagging a stable release.
We'll to keep this issue updated as we make progress! 🚀
The text was updated successfully, but these errors were encountered: