[Tinyos-1.2wg] 1.2 Requirements

[Ion Yannopoulos]

One of the first things we need to do is to decide what is actually 
going -in- the 1.2 release.  The ground rules as I see them, are:

In the core (tos/):
 - Every component must have a set of unit tests.
 - Every application must have a set of application-wide tests.
 - Every NesC file must at least have a document comment describing the 
interface or component's purpose and usage.  It should include the list 
of authors.
 - Every NesC file should have document comments describing its 
commands, events and tasks.
 - Nesdoc should generate wiring graphs for the entire system.
 - Every Java package should have a README/package.html
 - Every Java file must at least have a document describing the 
interface or class's purpose and usage.
 - Every Java file should have document comments describing its methods.
 - Javadoc should generate documentation for each Java application/tool.
 - Every C file should have a set of unit tests.

In contrib/:
 - As many projects as possible should follow the above.  Certainly ones 
that want to be labelled as stable must do so.  We wont be establishing 
that anything in contrib/ is supported, but we may be able to say that 
parts of it have at least been tested.

"Must", and "should" here are following the RFC usage: "must" is a 
requirement, "should" would be preferrable.

There's clearly a lot more here, especially in regards to which 
components should be tested first, and how to test them.  There's also 
more not covered here.

Thoughts and comments?

Ion
_______________________________________________
Tinyos-1.2wg mailing list
Tinyos-1.2wg at Mail.Millennium.Berkeley.EDU
http://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-1.2wg