Release 2.0

[Jean85]

During #114 we started working toward a 2.0, with a dedicated branch. With that merged, 2.0 is compatible with HTTPlug 2 and PSR-18. What else do we want to add? I'll try to suggest some stuff and track it here. Maybe we can use a milestone?

• Update the docs/changelog
• Use PHP 7 language features, since it's now the minimum
  • Scalar type in method parameters and return types
• Remove deprecations
• Make all classes that are not intended to be extended final, verify that everything that is protected really needs to be protected

[sagikazarmark]

Good idea, added something too.

I would probably wait with tagging until we actually have a client that we can use with this package, but Guzzle adapters will probably be tagged by then.

[dbu]

👍 i edited the PHP 7 thing to be more concrete. did you have other things in mind? we should focus on potentially BC breaking things. we can optimize implementation constructs after 2.0 is released, but method signatures, visibility/removing deprecations and final etc are BC breaks that we want to do now.

[Jean85]

We should add #20 to this list.

[dbu]

there is https://github.com/php-http/client-common/milestone/3 - imho we should use the milestone to group all tasks for the 2.0 release.

[mxr576]

Any ETA for the 2.0.0 release?

[Nyholm]

We will release it before Wednesday.
@mxr576 Do you want to help review it and make sure every thing is correct?

[mxr576]

Yes, I am happy to help. I am also updating my library's dependencies in this week.
I'll give it to try to #141 which was a follow up on #113. Of course, validate all other changes in the master branch with my libs automated tests.

[Nyholm]

That would be great.

Im pretty sure that current dev-master will be tagged 2.0. We just need more people testing it and review it.

[dbu]

i tagged 2.0.0-RC1 just now. please report issues if you can find any.