[Tinyos Core WG] 2.1 release plans

[Kevin Klues]

Also apps under tutorials.  Not sure what some of these are, but
LowPowerSensing is refered to in Tutorial 16, Printf is refered to in
Tutorial 15, and SharedResourceDemo is referred to in Tutorial 8.
There's also the RssiDemo tutorial written by Dimas Abreu Dutra that I
pushed in there.  The tutorial for that one is on the wiki as well.

Oh, and its no longer tests/TestArbiter.  Its tests/arbiter, with two
test applications underneath.

Also, whats the story with all the other applications?  Do they jsut
sit here in cvs and not become part of the release?

Kevin

On Thu, May 22, 2008 at 8:53 PM, Philip Levis <pal at cs.stanford.edu> wrote:
> We're not at the point of code testing yet, but since we have a few
> people who are new to the release process, I thought I'd sketch how it
> works.
>
> Right now, we have a short list of outstanding bugs that need to be
> fixed and code that needs to be added. The hope is to complete these
> by the end of June. Once everyone signs off on their parts, we get to
> testing and validating the code base. This has become a little easier
> with tutorials moving to the wiki.
>
> When the tree is ready, I'll tag it with a non-branch release tag, to
> make sure everyone is testing the same code. You check in fixes to the
> head of the main tree, and mail the list about them. Once we've gone
> through the first iteration, I tag again, and we test again, to make
> sure that one person's fix did break another person's test.
>
> There are two kinds of testing: platform and application. There's a
> list of applications that each platform owner needs to test on the
> respective platform. This means compiling (no warnings), running,
> using the associated tools, etc. There's a small number of apps that
> other people test (e.g., the net2 apps); most are handled by core.
> Application testing involves looking at application source code and
> making sure that it follows TEP 3, is documented, etc.
>
> When I send out the message, it will look something like this. The app
> list is tentative; I'm sure I've missed some; if so, just mail me and
> I can add them.
>
> ---
>
> We are now at this stage of the release process. I have tagged the
> repository with
>
> xxxxxx
>
> Please, everyone, begin testing. Responsibilities are:
>
> A platform owner MUST, by XXX:
>
> 1) Test that each of the below applications work
> 2) Report to the list that they have done so
>
> An application owner MUST, by XXX:
>
> 1) Ensure that the application meets the naming conventions of TEP 3
> 2) Ensure that the application has a README that accurately describes
> its operation
> 3) Report to the list that they have done so
>
> If you *absolutely cannot* do the tasks assigned to you, speak up as
> soon as possible.
>
> The platform owners are:
>
> mica2/mica2dot: (need a volunteer)
> micaZ: Phil
> telos: Kevin
> intelmote2: Brano
> tinynode: Maxime
> eyesIFX: Vlado
> iris: Janos
> shimmer: Konrad
>
> The applications and their owners are as follows. All networking
> applications should be tested with and without low power listening,
> with a 500ms check interval:
>
> AntiTheft: Phil (note platform-specific)
> BaseStation: Phil
> Blink:  Vlado
> Null: Phil
> Oscilloscope: Konrad
> Powerup: Janos
> RadioCountToLeds: Mike
> RadioSenseToLeds: Mike
> tests/cc2420: David M
> tests/deluge: Vlado
> tests/storage: Razvan
> tests/TestAdc: Jan
> tests/TestAM: Kevin
> tests/TestArbiter: Kevin
> tests/TestLPL: David M
> tests/TestPrintf: Phil
> tests/TestSerial: Miklos
> tests/TestSimComm: Razvan
> tests/TestSimTimer: Mike
>
> These apps will be handled by net2 (do not need to be tested by
> platform owners):
>
> MViz: Phil
> MultihopOscilloscope: Om
> MultihopOscilloscopeLqi: Om
> TestNetwork:  Om
> TestTymo: Romain
> tests/TestDissemination: Om
> tests/TestDIP: Phil
>
> -----
> _______________________________________________
> Tinyos-2.0wg mailing list
> Tinyos-2.0wg at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg
>



-- 
~Kevin