Hello Jan,
I thought of kicking v1 out of the tree on the long term. Maybe we should move the current version to tdma-v1 while hacking on v2.
I would suggest to not kick out tdma-v1 but to rename its directory to something like tdma-v1 as long as it is usable.
This is how the current tree look like:
stack/rtmac/tdma -> new version 2 stack/rtmac/tdma-v1 -> old, unmodified version 1
At least for 0.8.x, this will remain so.
However, I don't see a reason for keeping v1 in the main trunk when v2 can fully replace it. v1 has known problems during setup und shutdown while v2 will avoid these problems by design. Furthermore due to the new RTmac frame revision 2.0, there is already now no more backward compatibility to older RTnet versions. You either have to stay at 0.7.1 or earlier, or you have to switch completely. We are still pre-1.0, so we think that this step is acceptible to avoid unnecessary legacy overhead in the code. Of course, we will have to think about such steps differently after releasing 1.0!
What is your concrete concern about dropping tdma-v1 in 0.9.x - even if tdma-v2 will be stable then?
Jan
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ RTnet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-users
