Re: Persistent Volume API Change

I'd vote for fixing the bug directly w/o a deprecation period, because a framework is always supposed to registered with proper principal to perform various operations. As long as we clearly document this in upgrade.md, operators should be able to properly fix their framework usage and ACL,

Persistent Volume API Change

Hello all, I'm currently working on MESOS-5005 , which is fixing a small bug in the persistent volumes API. When a new persistent volume is created, a `DiskInfo` message is included in the disk resources of the volume. Nested within another message