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
This is a master issue for tracking the upcoming 1.0 release of Isahc.
Isahc's API has pretty much settled into a comfortable position at this point and has no outstanding obvious API deficiencies any more, so now is a great time to make the few pending breaking changes we want to make and release the next version as 1.0.
I've decided that we will not wait for our public dependencies to reach 1.0 first even though it is recommended, because we have very few such dependencies and they move slowly anyway.
Timeline
1.0 is scheduled to be released before the end of December 2020.
Determine whether the body type ought to change further
Review serialization/deserialization ergonomics. We don't need to implement Unified body encoders/decoders #211 as the current methods can be changed to convenience methods around a more powerful API later, but we should make sure that the existing methods make sense with that in mind.
Isahc 1.0 will encompass a stabilization of the API, and will include full Future and async/await support. The plan is to release a new minor version with the updated API after futures are stabilized in the standard library. After that, let the API soak for a month leaving room for any fixes that might be needed or changes that need to be made to the design. After that we'll release version 1.0.
Most of the open feature requests will be deferred to post-1.0 (though the API needs to keep these requests in mind). The things that must be done before 1.0 are tracked in this milestone: https://github.com/sagebind/isahc/milestone/3
Preparation for 1.0 will be done on a separate branch from master, since Isahc is already a "stable" library and requiring nightly is not on the table.
The text was updated successfully, but these errors were encountered:
Note to self: 1.0-beta.1 will be scheduled for December 12, if everything goes as planned. We will release at least 1 beta to be used early to ensure everything is ready and the new API designs are working as intended.
This is a master issue for tracking the upcoming 1.0 release of Isahc.
Isahc's API has pretty much settled into a comfortable position at this point and has no outstanding obvious API deficiencies any more, so now is a great time to make the few pending breaking changes we want to make and release the next version as 1.0.
I've decided that we will not wait for our public dependencies to reach 1.0 first even though it is recommended, because we have very few such dependencies and they move slowly anyway.
Timeline
1.0 is scheduled to be released before the end of December 2020.
API
Release tasks
Original description
Isahc 1.0 will encompass a stabilization of the API, and will include full
Future
and async/await support. The plan is to release a new minor version with the updated API after futures are stabilized in the standard library. After that, let the API soak for a month leaving room for any fixes that might be needed or changes that need to be made to the design. After that we'll release version 1.0.Most of the open feature requests will be deferred to post-1.0 (though the API needs to keep these requests in mind). The things that must be done before 1.0 are tracked in this milestone: https://github.com/sagebind/isahc/milestone/3
Preparation for 1.0 will be done on a separate branch from
master
, since Isahc is already a "stable" library and requiring nightly is not on the table.The text was updated successfully, but these errors were encountered: