Update stack/builder for Symfony 3 compatibility

I'll try to get this issue w/ stack/builder resolved this week.

Do we have to wait on the stackphp release or can we just use dev-master in composer.json? I forgot if we have a policy about non-stable dependencies in composer, do we have a doc page or something else for that?

Alternatively we can just fork stackphp and make our own stable release, but I think depending on a dev version is the lesser evil.

I don't think we have a policy around that. IMHO creating a fork with different stable versions would be just more confusing.

IMHO we should not have to wait for an upstream release, but I'm not sure whether there might be a policy around that.

Agreed, so let's go ahead with the dev version in composer.json.

Patch does not apply anymore, rerolled. I also added the specific git hash to composer.json to make sure people always get this version when they mess with composer update.

IMO this is RTBC, can someone double check and change the status.

Fixed issue summary.

Patch does not apply anymore, rerolled. I also added the specific git hash to composer.json to make sure people always get this version when they mess with composer update.

Good idea!

A new release is tagged: https://github.com/stackphp/builder/issues/21.

I apologize on the delay for this. Life happened and I'm in the process of getting someone else to help maintain StackPHP going forward. Hopefully this will get you unstuck for now but if there are issues with this build let me know and I'll see if I can get around to it more quickly this time around.

Thanks for your patience.

Cool, so we only need to update composer.lock.

@simensen
No worries, life is always more important than this opensource thing. Thanks a ton!

It's cool to see when the version updates are actually small!

Committed/pushed to 8.2.x, thanks!

Since this paves the way for Symfony 3, may be worth calling out in the release notes.