From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] development flow
Date: Mon, 31 Aug 2009 13:26:29 +0800 [thread overview]
Message-ID: <200908311326.29339.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20090830202306.GB2410@pandem0nium>
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
next prev parent reply other threads:[~2009-08-31 5:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 1:36 [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Linus Lüssing
2009-08-30 1:59 ` Linus Lüssing
2009-08-30 7:37 ` Andrew Lunn
2009-08-30 20:23 ` Simon Wunderlich
2009-08-31 5:26 ` Marek Lindner [this message]
2009-08-31 5:50 ` [B.A.T.M.A.N.] development flow Andrew Lunn
2009-09-01 18:47 ` Marek Lindner
2009-09-02 6:18 ` Andrew Lunn
2009-09-03 6:06 ` Marek Lindner
2009-09-08 16:01 ` Andrew Lunn
2009-09-08 17:54 ` [B.A.T.M.A.N.] mailing list migration (was: development flow) Marek Lindner
2009-09-18 21:14 ` Jacob Marble
2009-09-18 21:19 ` Jacob Marble
2009-09-19 7:59 ` Andrew Lunn
2009-09-28 3:29 ` Jacob Marble
2009-09-28 3:31 ` Jacob Marble
2009-09-28 5:03 ` Andrew Lunn
2009-09-28 6:12 ` Jacob Marble
2009-09-29 5:06 ` Jacob Marble
2009-09-29 5:25 ` Andrew Lunn
2009-09-29 9:19 ` Marek Lindner
2009-09-29 15:56 ` Jacob Marble
2009-09-29 16:14 ` Sven Eckelmann
2009-09-30 5:39 ` Jacob Marble
2009-09-30 19:27 ` Marek Lindner
2009-09-29 15:38 ` Jacob Marble
2009-08-30 19:55 ` [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Simon Wunderlich
2009-08-30 20:15 ` Andrew Lunn
2009-08-30 21:47 ` Linus Lüssing
2009-08-31 5:28 ` Andrew Lunn
2009-09-01 20:47 ` Linus Lüssing
2009-09-04 18:58 ` Linus Lüssing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908311326.29339.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).