I'm concerned that after all the work is done, it will be hard to merge the M2 changes from the branch to the trunk. SVN doesn't seem to have particularly good handing for merging changes that involve a lot of subsequent adds, deletes, moves, etc. When this stuff gets complex, more often than not, I've had to just whack the old tree and check out a fresh copy.
So we could all shift to working out the kinks in the M2 branch as CTR and then vote to make that branch *into* head under the rules for revolutionaries. But really, I think this just emphasizes the limitations of RTC for the kind of work that's going on for 1.2. Thanks, Aaron On 7/3/06, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
Hi, After having read so many emails with frustration and disgust, I think we could get rid of these shortcomings and do the migration in a branch - m2migration or alike. The idea of the branch would be to loosen up the RTC rules that are bound to the trunk and let people experimenting - do the migration without having to follow RTC, preparing patches that don't work for everyone, but often very temporarily until they're again fixed and improved. Thoughts? Jacek -- Jacek Laskowski http://www.laskowski.net.pl
