On 09:03 Fri 17 Jun , Øyvind Harboe wrote: > On Fri, Jun 17, 2011 at 8:25 AM, Jean-Christophe PLAGNIOL-VILLARD > <plagn...@jcrosoft.com> wrote: > > On 08:17 Fri 17 Jun , Ųyvind Harboe wrote: > >> Some questions/comments: > >> > >> - if we look at the current way we work with OpenOCD, we just > >> commit stuff to the master branch without regards to a release. > >> I would like this to continue in the same manner, which I don't > >> think is in conflict with what you write. > > in this case you do it on the next branch > > > > the master branch is the release branch it's like this in most of the > > project > > > > buildroot, kernel, barebox, u-boot etc... > > I think doing things somewhat similar to other projects, but not exactly > the same is OK. OpenOCD is very unlike Linux: resources, pace, quality, > etc. > > I'd like to see the master branch used exactly as today with a pull > request being sent from the release manager when the release is ready... 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 Best Regards, J. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
