Hi,

libtuxdriver must be in RC state for the end of june. I would to close the improvement of functionnalities in order to passe it in 0.0.1 beta version soon.  What is the way for this ? Creating a branche for finalizing the V0.0.1 and leave the trunk for 0.0.2 ?

Rémi

I haven't made any API changes. I do want to finish off the parser changes (they are already partially committed), but I have not too much time at hand the next few days (and we are getting some fine weather).

My suggestion would be to branch after these changes are done, then branch 0.0.1 for maturing and leave trunk for 0.0.2

(actually apart from the eventing and some smaller optimisations I expect not too much activity on the driver anyway).

I decided to borrow some time to finish the cmd_parser changes.
Feel free to review it.

It passes the tests from use_tux_driver, but some more indepth testing could be done (it is quite possible that somewhere along the line I made a copy&paste error by forgetting to edit the name of a macro or so).

I still would like to have a little bit of time (e.g. until next tuesday) to see if I can update the eventing code (mostly moving it to sw_status).
I am not planning on changing the API right now, but instead of doing all the tests in mouth etc, I would like to move them to sw_status (where I then add an additional field delta or so which contains the delta that is needed before the event is fired).

(and if needed feel free to contact me by email/msn/irc to discuss this).

FM

I've rethought about this.

What if I make my status changes next week and after that we agree only to go into a maturing phase where only bugs are fixed and no functional modifications or esthetical changes, before branching off?
Issue is that if we side branch all bugs that are discovered need to be repaired at two places.

(And if someone does decide on a major overhaul, we can still decide to make a side branch on the current version).