...
One outcome of the meeting of VIVO sponsors at the March, 2014 DuraSpace Summit even in Washington was a request to move to a regular release schedule where timing would be predictable and the determination of new features included in each release – if a feature was deemed to be ready, it would be included; otherwise, it would wait only if ready. Any feature not on target to be finished by the code freeze data would have to be deferred until the next release.
A schedule of two releases per year targets a May code freeze for a June release (VIVO 1.7), and a November code freeze for December release.
...