RFC: Roadmap

[andig]

1.0 stable:

• upgrade mkraemer/pcntl (Allow mkraemer/react-pcntl 3.0 #299)
• include static and middleware bridges in core (Provide default Psr7/Psr-15 and Psr7/invokable bridges plus static web bridge #278)
• some sort of end-to-end testing of process manager, client and httpkernel bridge (Integration test #298)
• drop support for concurrent requests (Remove concurrent requests #302)
• upgrade react/http to 0.8 when it's released (Upgrade react/http #310)
• refactor source code (Refactor slave handling #307)
• add src folder (Add src folder #309)
• release httpkernel 1.0 (Require stable php-pm php-pm-httpkernel#77)

1.1:

• drop php 5.6 (Upgrade http-interop #335)
• upgrade any react packages to ^1.0 versions when available
• upgrade http/interop (Upgrade http-interop #335)

Other topics:

• fix zend and drupal bridges for Psr7 (PRs welcome)
• code style checking (Add style and static analyzer checks #301)
• unit tests (PRs welcome)
• symfony 4 support (Update symfony usage php-pm-httpkernel#87, tbd)

[dzubchik]

I would like to propose adding a bit of stability to development process.

1. create tag 0.0.1 on master
2. create branch dev
3. add branch alias 0.1.x-dev to dev branch

And I do not understand profit with separating adapters as it adds more dependencies. I propose to use structure as in monolog library. All adapters in one place, but if you want to use some of them you should install concrete dependency by yourself.

[andig]

I would like to propose adding a bit of stability to development process.

Totally agreed. However, react/http is in flux, having changed it's http server class name just last night (reactphp/http@d660095). In this situation a tagged version- whatever it is- doesn't help us any. Tagged react version is a requirement for tagging here imho.

All adapters in one place, but if you want to use some of them you should install concrete dependency by yourself.

Could you elaborate?

[kelunik]

If Symfony releases a breaking change, you either have to version the adapter class and keep the older version or release a new major version of php-pm, which would also affect all others.

[dzubchik]

@kelunik , agree with you that it is not the best idea to put adapters to core.

So maybe we can just create some adapter's boilerplate with some tests, code-style rules, etc?

[dzubchik]

One more propose is adding strict code-style(php-code-fixer) and static analyzer checking(phpstan).

[abdouz]

Hi everybody,
Any updates about the latest version based on react http 0.8?

[andig]

Any updates about the latest version based on react http 0.8?

We have pretty much everything merged that was targeted for 1.0. I'd a appreciate a bit of time for the extensive changes to settle, fix a couple of bugs that might pop up and then .... release

[marcj]

Yes, let's test a few days first. Will do over the holidays.

[skonsoft]

Thank you for this great Job. We are wainting !

[andig]

Yes, let's test a few days first. Will do over the holidays.

@marcj Great. Releases are drafted and waiting for you. HttpKernel needs one more PR, already assigned to you.