[Tinyos-devel] AM ID allocation TEPs

[Vlado Handziski]

Apart from the version metadata in the TEP headers, the release and the TEP
finalization processes are not coupled. We should just start the review
process for TEP 4 and 135. We are in code-freeze for 2.1 so the TEP
finalization process won't have any additional influence on 2.1. Or am I
missing something?

Vlado

On Fri, Jun 20, 2008 at 18:10, Omprakash Gnawali <gnawali at usc.edu> wrote:

> I agree about the sequence but what about the process? Potentially
> something like TEP 135 might not be ready just before the release
> which makes it problematic to have it go through some weeks of
> community feedback.
>
> Considering we don't have a few weeks before the 2.1 release, what to
> do about 4 and 135? Maybe start the community feedback and wait until
> 2.1+?
>
> - om_p
>
> On Fri, Jun 20, 2008 at 8:40 AM, Vlado Handziski
> <handzisk at tkn.tu-berlin.de> wrote:
> > This should be done sequentially, i.e. TEP 135 should be finalized only
> > after TEP 4 is.
> >
> > Vlado
> >
> > On Fri, Jun 20, 2008 at 17:14, Omprakash Gnawali <gnawali at usc.edu>
> wrote:
> >>
> >> Now there are two AM ID allocation related TEPs in the repository. TEP
> >> 4 talks about the process and TEP 135 documents the IDs used in TinyOS
> >> 2.1. I think TEP 4 should go through the standard process of
> >> finalizing the TEP. I think TEP 135 can be finalized without the
> >> standard shepherding because it simply documents the IDs used.
> >> Thoughts?
> >>
> >> - om_p
> >> _______________________________________________
> >> Tinyos-devel mailing list
> >> Tinyos-devel at millennium.berkeley.edu
> >>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-devel/attachments/20080620/1b3251ba/attachment-0001.htm