Crow's February Plans
Published on February 5, 2022 by Farook Al-Sammarraie
Let's get the bad news out of the way. Unfortunately January did not go as expected.
The reason behind that is a particular bug was made apparent during the changes to the HTTP parser. That bug dragged the development for much longer than anticipated.
The fix (along with changes to the parser) are expected to be submitted soon.
Looking at the rest of the January plan, v0.3+4 was released independently due to security vulnerabilities that were found. And v1.0 was not released.
Moving on to the plan for this month, it's a mixed bag of large and small features. With the parser changes and Per request middleware (Thanks to dranikpg on GitHub) being the larger changes. And smaller changes including improvements to mustache, multipart messages, and JSON.
Once all those and the release scripts for VCPKG and Conan are dealt with. v1.0 is expected to come out.
Thank you to everyone who supports Crow, financially or through code and expertise. You took this project from an idea and made it into a reality.
The reason behind that is a particular bug was made apparent during the changes to the HTTP parser. That bug dragged the development for much longer than anticipated.
The fix (along with changes to the parser) are expected to be submitted soon.
Looking at the rest of the January plan, v0.3+4 was released independently due to security vulnerabilities that were found. And v1.0 was not released.
Moving on to the plan for this month, it's a mixed bag of large and small features. With the parser changes and Per request middleware (Thanks to dranikpg on GitHub) being the larger changes. And smaller changes including improvements to mustache, multipart messages, and JSON.
Once all those and the release scripts for VCPKG and Conan are dealt with. v1.0 is expected to come out.
Thank you to everyone who supports Crow, financially or through code and expertise. You took this project from an idea and made it into a reality.
❤️ 1