> so we do two tree the next tree (yours) and the release tree > > if multiple maintainer eed to merge code together they will send it the the RM > in his next branch > > the description will be what must follow the release tree for the other tree > the maintainer manage his own way
I am struggling a bit following the above, but I think we agree: - development goes on in master like it always has done - you create a fork at the openocd mirror and create a release branch there. You pick whatever you want from the master branch or whatever patches posted that you think should go in and generally run the release cycle. - once you're done with the release, I pull it from you and push it to the official openocd repository. The advantage of this approach is that we can work independently and that you can get started today, we both have everything we need. For intrusive and dangerous changes, we should synchronize, but most changes to OpenOCD are small these days. Tomek's work excepted... -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
