[mylyn-reviews-dev] Managing R4E model changes, new branch.

[Miles Parker <miles.parker@xxxxxxxxxxx>]

I'd like to merge are model changes asap as managing the gerrit trauma on further changes will be unmanageable otherwise. But they really should be in a branch as they are going to break everything model related. Unfortunately, gerrit defaults to master branch and there doesn't seem to be anyway to change the dest branch post hoc. (See http://code.google.com/p/gerrit/issues/detail?id=117)

(This doesn't apply to Reviews proper as that is an non-breaking change.)

So, we can put the breaking changes in master and create a backward compatibility branch or I can resubmit everything (again, sigh!) under a new branch targeted review. In the latter case, we'll need to setup some kind of build support for the new branch. I don't expect the period I spend working on this to be that long. I'm almost considering doing it all in that gerrit branch, but there is too much code to contribute unless I get committer rights really soon. (Perhaps we should do that now for R4E?)