Roadmap to stable v1.0.0

[clue]

Let's face it, this project is currently beta, but has been used in production for years

We're currently following a v0.X.Y release scheme (http://sentimentalversioning.org/).

We should finally make this stable and fully adhere to SemVer and release a stable v1.0.0.

To a large extend, a stable v1.0.0 helps making BC breaks more explicit and thus the whole project more reliable from a consumer perspective. This project is actively maintained and has received some major updates in the last weeks and has some major updates planned in the next weeks. Given our current versioning scheme, we'd like to ensure all anticipated BC breaks will be merged before the planned v1.0.0 release.

As such, I've set up a roadmap that enlists only the major changes for each version among with planned release dates towards a stable v1.0.0 release:

v0.4.4 ✅

• Released 2017-02-13
• Headers PSR-7 and case-insensitive
• Version constraints
• Stream empty data events and back-pressure

v0.5.0 ✅

• Released 2017-02-16
• Request PSR-7 methods
• Reduce public API
• Socket component v0.5 and secure HTTPS

v0.6.0 ✅

• Released 2017-03-09
• Chunked transfer encoding and Content-Length
• Stream data, end and close behavior
• Stream v0.5 API
• HTTP/1.1 and HTTP/1.0
• No longer considered beta quality

v0.7.0 ✅

• Released 2017-05-29
• Streaming PSR-7 support
• Request-In-Response-Out callbacks

v0.8.0 ✅

• Released 2017-12-12
• Full PSR-7 support
• Form submissions, including POST fields and file uploads
• Middleware request handler arrays

v1.0.0 ✅

• Released 2020-07-11
• New HTTP client
• Clean up Server APIs
• LTS

This ticket aims to serve as a basic overview and does not contain every single change. Please also see the milestone links and the CHANGELOG for more details.

Obviously, this roadmap is subject to change and I'll try to keep it updated as we progress. In order to avoid cluttering this, please keep discussion in this ticket to a minimum and consider reaching out to us through new tickets or Twitter etc.

[clue]

Updated now that the v0.5.0 release is out

https://github.com/reactphp/http/milestone/2

[WyriHaximus]

With no changes between 0.8.0 and 1.0.0, does it make sense to go full PHP 7+, scalar type hints, return type hints etc etc, with 1.0.0? Making 0.8.x targeted for PHP 5 and 1.x for PHP 7.

[clue]

go full PHP 7+, scalar type hints, return type hints etc etc

I'm open for this and would like to discuss the pros and cons of this in a separate issue 👍 Do you feel like filing an issue to spark the discussion?

That being said, unless we bring up some very good points for this, I would tend to vote against getting this in for 1.0.0 yet. We may totally release a v2.0.0 a month after v1.0.0 though, if we see this provides substantial benefits 👍

My idea here would be to provide some (limited) long-term support for older versions on the stable v1 series (similar to how our Promsies work) and then look forward for upcoming major releases 👍

[WyriHaximus]

That being said, unless we bring up some very good points for this, I would tend to vote against getting this in for 1.0.0 yet. We may totally release a v2.0.0 a month after v1.0.0 though, if we see this provides substantial benefits 👍

That makes perfect sense, I'll file an issue on the meta repo 👍

[clue]

Updated the upcoming v0.6.0 milestone to also include the Stream v0.5.0 changes that are planned: reactphp/stream#67

[clue]

Updated now that the v0.6.0 release is out 🎉 🎉

[andig]

I'm really happy about the progress react is making lately. However, I'm wondering what the approach will be towards using ServerRequestInterface instead of RequestInterface. Ringcentral currently doesn't have it and also does not have any PR queued up. If that the only blocker would moving to guzzle be a cure?

[clue]

@andig Do you mind if we move this discussion to #28 instead? Afaict @legionth has made some very good progress with the ServerRequestInterface and it basically only adds a few methods to the existing RequestInterface, so I don't really see this blocking the process for much longer anyway 👍