@mindplay-dk no idea, it needs to be voted by the FIG. However in its current form (
ContainerInterface) I think it's risky to try to make it go a voting phase. What we are working on (service providers) addresses the main concern raised on the FIG. So I think when service providers is ready, it will be a good time. However we have no idea of a time frame. But the good thing is that container-interop works great, even though it's not a FIG standard. So from my POV there is no reason to rush anything, we have what we need today already. The only thing missing is maybe that it's not implemented by Symfony and Laravel but it can be worked around
that would be great! we are discussing on the definition-interop channel though (https://gitter.im/container-interop/definition-interop) feel free to join! The main thing we need right now is to involve framework and container developers to gather feedback: is it easy to implement support in containers? is it limited/missing features? is it easy to write modules? can we do what we do today with this solution? are performances OK? If you find anything wrong feel free to open an issue on github, or chat in Gitter as well it's a good way to discuss informal stuff