On Monday 31 August 2009 04:23:06 Simon Wunderlich wrote:
Usually we have stable versions (e.g. batman-adv 0.1) with a specific format, and an ongoing development in the svn trunk. Maybe we should do the same for future kernel development - maintaining one packet and algorithm version in the kernel, and further develop the algorithm on our own (e.g. in a git tree or with sets of patches)? In this case, we should post the current batman-adv to the list when 0.2 is stabilized and finished. Mainline algorithm should only be changed when we reach a new stable version.
Actually, I came to a similar conclusion: We "only" submit stable versions to mainline (including stability fixes) whereas the development stays outside of the official linux tree. That way we can keep our development speed without worrying too much about compatibility. When we are getting to the next stable release we can think about how to soften the transition.
More ideas / opinions ?
Regards, Marek