Re: [B.A.T.M.A.N.] development flow

Andrew Lunn
2009-09-02T06:18:22Z

> > I would also suggest we post our patches as soon as possible, so we
> > start getting feedback from the kernel community about what else needs
> > adding to the TODO list etc.
>
> Yes, when and where should we post it ? Should the mailing list be
> migrated at that point (I felt a consensus concerning the ml move) ?

We should post them to GregKH. That is what he said. What happens
after that i don't know. Maybe he has an internal team which will do a
review? Maybe it goes straight into staging and anybody who is
interested can review the code.

I would say the list needs to be open before we post the patches. We
don't want valuable comments going lost, or annoying people who do
reviews by bouncing there comments etc.

> It might be a good idea to maintain the ToDo list in the wiki - what do you
> think ?

I say the master has to be in the sources, where anybody who reviews
staging will see. The Wiki copy is just a mirror, with a big comment
that its not the master, all changes should first go into the sources
TODO list which is then re-imported into the Wiki.

Maybe we need to branch SVN, or we setup a git tree. I already have
local changes just so that it builds with linux-next.git from
Saturday.

Andrew