Hi Peter, Thanks for the comments. I think addressing them will clarify the policy greatly.
> On Feb 14, 2017, at 5:21 PM, Peter Saint-Andre - Filament > <[email protected]> wrote: > > On 2/14/17 5:09 PM, aditi hilbert wrote: > >> https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy > > Thanks, Aditi - as with everything Mynewt, this is very well done. > > A few small comments: > > 1. We might want to explicitly define the meaning of "releases that are still > supported" (mentioned under Release Schedule); for instance, is it only the > current major release, or one or two prior releases as well? The section on > Backwards Compatibility talks about active and deprecated features at a more > granular level, but not the definition of supported releases. > This may be different with each major release. For example, 1.1 may be supported but 1.2 might not (say there’s a horrible bug). I will add language about supported releases and when a release may not be supported. > 2. Is there an API / feature state for Obsolete in addition to Active and > Deprecated? This ties in with my next point… > > 3. Perhaps some mention of documentation is in order? For example, will > up-to-date documentation accompany each code release either concurrently or > within some reasonable timeframe? (The tie to the previous point is that we > might want to have documentation of previous API snapshots as things change > over time.) Agreed. We are working on releasing documentation that is versioned for each release and there will be links for them from the site. So the user will know when an API was deprecated and go back to that release documentation if he/she is still working with older release. I will work on some language around this. > > Kudos to the Mynewt team for this extremely clear and comprehensive policy > description. > > Peter > > -- > Peter Saint-Andre > https://filament.com/ > thanks, aditi
