public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Axel Neumann <axel@open-mesh.net>
To: pele@balorda.com,
	The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] batman 0.3 and batmand-exp-0.3
Date: Wed, 21 Nov 2007 21:00:05 +0100	[thread overview]
Message-ID: <200711212100.05898.axel@open-mesh.net> (raw)
In-Reply-To: <000601c82c52$1df6c0b0$59e44210$@com>

Hello,

sounds like you made some good experience with the batman-exp branch. Thats 
really cheering to hear. Just, let me add some words regarding your 
understanding of the different branches.

batman-exp has started as a branch to make batman more configurable - e.g give 
the user more control about the system integration and even twist the core 
routing algorithm.  
Of course more flexibility also tends to make things more complex.
The majority of the developers did not wanted to have the bunch of optional  
configuration options in the standard batman branch, thats why these features 
were realized in a different branch. 

Particularly its possibility to experiment with the core routing metrics has 
lead to the extension "-experimental". Unfortunately, this has caused some 
people to think that the maturity of batman-exp is less advanced than the 
standard branch. This is NOT the idea, nor is it the other way around. Just 
two different branches, supposed to coexist and enrich each other.

Of course such a biased opinion tends to hurt a bit, and for the release I am 
already considering to rename it to something like -x or -exp. So it may 
considered as batman experimental, expert, extremely professional, or what so 
ever. But anyway, its just a name.


Approximately since the release of batman-0.3-alpha we have started to develop 
some new mechanisms to make the core routing algorithm more aware of 
asymmetric links and other stuff. And we had two different ideas to achieve 
this. It turned out, that one approach was implemented in the standard branch 
and the other one in the exp branch. 

I think that both approaches definitively have their charm and their 
shortcomings. And it requires the feedback of the users to further trigger 
the evolution of these approaches. I am very grateful for that and any other 
feedback, criticism, bug report, etc.

Regarding the versioning (0.3/0.4/apha/beta/rc1...). exp 0.3-alpha might be a 
bit conservative. However, there is a very small list of other features on my 
todo list which i would like to add before the code is freezed.

thanks,
axel


On Mittwoch 21 November 2007, Predrag Balorda wrote:
> I have been using the exp branch for over 2 weeks now and it is working
> nicely. OK my set-up is not huge, only 4 batman-enabled nodes with
> additional 6 repeaters as clients to batman nodes. Now I would like to know
> when will someone decide to kill off the 0.3 beta and continue with exp 0.3
> as the only batman? Maybe it's time to name it batman 0.4 and get rid of
> the "experimental" designation altogether (you even got the official
> ports)?
>
> I even believe exp can be now released as another stable version.
>
> Best regards to everyone on the list,
>
> Pele
>
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n



  reply	other threads:[~2007-11-21 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  7:30 AW: [B.A.T.M.A.N.] wrong ip rules Marek Lindner
2007-11-14 12:57 ` Aaron Kaplan
2007-11-14 16:08   ` tetzlav
2007-11-20 16:33     ` Marek Lindner
2007-11-21 15:20       ` [B.A.T.M.A.N.] batman 0.3 and batmand-exp-0.3 Predrag Balorda
2007-11-21 20:00         ` Axel Neumann [this message]
2007-11-14 14:49 ` AW: [B.A.T.M.A.N.] wrong ip rules / tunnel crashes tetzlav

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=200711212100.05898.axel@open-mesh.net \
    --to=axel@open-mesh.net \
    --cc=b.a.t.m.a.n@open-mesh.net \
    --cc=pele@balorda.com \
    /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