On Dec 16, 2007 12:34 PM, Kevin Klues <[EMAIL PROTECTED]> wrote: > > My solution to all this would be to try and convince everyone to switch > over to tinyos-2.x, but I realize that some people are reluctant to do so > right away. Many of the crossbow sensor drivers only exist for tinyos-1.x, > and many users have written code for their own applications that relies on > the way the 1.x task scheduler operates (which is quite different than the > 2.x task scheduler). Code between the two versions is therefore > unfortunately not backwards compatible. So whats the right answer here? Do > we need someone who is really invested in tinyos-1.x to step up and become > the official maintainer of the tinyos-1.x tree -- fixing bugs, etc. as > they come in and pushing out new releases that have the bug fixes in them? > Or would it be better to start motivating people to start porting everything > over to tinyos-2.x, so that their reliance on 1.x slowly fades away? >
Yup. At one point in time there was a notion of a 1.2 release working group (http://tinyos.net/scoop/special/working_group_tinyos_1-2). But this group hasn't been active for years. Speaking from the stand point of a XubunTOS maintainer I'd like nothing more then to see TinyOS 1.x be officially put into a sunset mode. Keeping 1.xsupport in XubtunTOS takes 10 times the effort of supporting 2.x. Mostly because we've forgotten more about 1.x then we remember. There is significant code rot in the tree. Contrib is a mess. On the other hand you're right many of the protocols are being left behind. TinyOS as an largely academic project means those protocols won't be ported. Companies aren't likely to pay for these to port, they want new chipset support, or improving on 2.x. Maybe generate a wish list and have classes port the best of 1.x. Student labor is just about the right price... I'd imagine this is something the Alliance and probably Core should make a decision on. I imagine the "right" answer is to sunset official support for 1.x (toolchains, install, everything). At this point the amount of support for 1.x is just a band-aid anyway. Rip it off and be done with it. A brief sunset period allows people to transition away or create some community support for a 1.2 project. Then after the sunset, its time to move on. The code will always be available at SourceForge so people who join the community can always look back. The last version of the supported tools can be available to people who linger. But the new members of the community will start in the right direction. They will have a reason to port what they need across the dead code barrier. My two cents. Chad
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
