COmanage Users List

[Benn Oshrin <>]

Hi all,

By way of an update, we've revised the roadmap slightly, and are now 
expecting the following upcoming Registry releases:

v3.2.0: Release Candidate due probably next week
v3.3.0: New features, 1Q19
v4.0.0: Some breaking changes in anticipation of the framework migration
v5.0.0: Framework migration (and additional breaking changes)

One issue we've been discussing is how to not completely stop new 
feature development while the (lengthy) framework migration project is 
underway. This means we'll probably continue with feature releases while 
v5.0.0 development is underway, but try to limit too many new features 
as that will slow down the framework migration work and add technical debt.

One proposal we'd like to float is to require any new features 
development while the framework migration is underway to implement 
against both old and new codebases if

(1) The new feature will go into a release prior to v5.0.0, and
(2a) The relevant code to be updated has already been migrated for 
v5.0.0, or
(2b) New code segments (eg: new models) are being added

This would apply to both code and financial contributors. So (for 
example) if you submitted a pull request against v4.0.0, and the related 
code was already in the v5.0.0 tree, you would also be required to 
submit a pull request against v5.0.0. Alternately, if you were funding a 
new feature, you would be expected to fund work against both trees.

Once v5.0.0 is ready, this policy would no longer be in place.

We continue to welcome comments and feedback as we structure this work.

Thanks,

-Benn-