Friendly ping

I'm still not really sure why this is necessary. You already get the trailing metadata with the status.

@jtattermusch want to chime in? I think the key usability issue here is that the $status object returned from a call wasn't well documented. It's not a well defined class. So it wasn't explicit to the user that you can do $status->metadata.

@stanley-cheung it seems like documentation is the key thing here. I think adding a new method to the call might make sense, but we need to properly document when the property can be accessed.
In any case, if $status is not properly documented, we should add the documentation for all the fields/methods users might care about.

Fair enough. So we are OK with adding this getTrailingMetadata API, right? At least it will show up in the generated docs. But I also agree that we should document what fields/properties can be accessed in the $status object.

@jtattermusch please confirm my previous comment?

@stanley-cheung I confirm.

will need a rebase to give jenkins a kick

Re-based and PHP tests passed