summaryrefslogtreecommitdiffstats
path: root/.gitignore
AgeCommit message (Expand)Author
2014-05-18add modelBernhard Posselt
2014-05-15fix protractor testsBernhard Posselt
2014-05-15add makefile to build projectBernhard Posselt
2014-05-13add code coverage to php travisBernhard Posselt
2013-09-09ignore build in repos directoryBernhard Posselt
2013-09-09logBernhard Posselt
2013-06-12gitignore cache folderAlessandro Cosentino
2013-05-07added acceptancetest suiteBernhard Posselt
2013-04-22ignore xml files in js folderBernhard Posselt
2013-04-22adjusted gitignoreBernhard Posselt
2013-03-20added feedmaperBernhard Posselt
2013-03-20restored original gitignoreAlessandro Cosentino
2013-03-20findAll functions in the itemmapperAlessandro Cosentino
2013-03-18added new ingore fileBernhard Posselt
2013-03-16removed build js filesBernhard Posselt
2013-02-06added ignore files for gruntBernhard Posselt
2013-01-27merged the angularjs branchBernhard Posselt
2012-08-12removes the Everything folderAlessandro Cosentino
2012-07-02button to add feed; selection of a feedAlessandro Cosentino
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-25 06:39:43 +0000
"sb">`AsyncRead` and `AsyncWrite`. Tokio 1.0 will be released as soon as the APIs are proven to handle real-world production cases. ### Tokio 1.0 in Q3 2020 with LTS support The Tokio 1.0 release will be **no later** than Q3 2020. It will also come with "long-term support" guarantees: * A minimum of 5 years of maintenance. * A minimum of 3 years before a hypothetical 2.0 release. When Tokio 1.0 is released in Q3 2020, on-going support, security fixes, and critical bug fixes are guaranteed until **at least** Q3 2025. Tokio 2.0 will not be released until **at least** Q3 2023 (though, ideally there will never be a Tokio 2.0 release). ### How to get there While Tokio 0.1 probably should have been a 1.0, Tokio 0.2 will be a **true** 0.2 release. There will be breaking change releases every 2 ~ 3 months until 1.0. These changes will be **much** smaller than going from 0.1 -> 0.2. It is expected that the 1.0 release will look a lot like 0.2. ### What is expected to change The biggest change will be the `AsyncRead` and `AsyncWrite` traits. Based on experience gained over the past 3 years, there are a couple of issues to address: * Be able to **safely** use uninitialized memory as a read buffer. * Practical read vectored and write vectored APIs. There are a few strategies to solve these problems. These strategies need to be investigated and the solution validated. You can see [this comment][pr-1744-comment] for a detailed statement of the problem. The other major change, which has been in the works for a while, is updating Mio. Mio 0.6 was first released almost 4 years ago and has not had a breaking change since. Mio 0.7 has been in the works for a while. It includes a full rewrite of the windows support as well as a refined API. More will be written about this shortly. Finally, now that the API is starting to stabilize, effort will be put into documentation. Tokio 0.2 is being released before updating the website and many of the old content will no longer be relevant. In the coming weeks, expect to see updates there. So, we have our work cut out for us. We hope you enjoy this 0.2 release and are looking forward to your feedback and help. [pr-1744]: https://github.com/tokio-rs/tokio/pull/1744 [pr-1744-comment]: https://github.com/tokio-rs/tokio/pull/1744#issuecomment-553575438
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-25 06:39:43 +0000