The Serial HW flow control could have definitely impacted me because certain devices I connect to require HW flow control set and others don't.
Dan, how does the release cycle process normally work for you guys? Obviously there will be a number of Beta drops and then at some point it is deemed stable. What is normally the criteria you guys use for deeming it stable? Is it typically just after it has been in beta for a certain period without any regressions being reported? If so, how long is that typically?
I once built a software test team and process for a company, so just curious to better understand the cycle so I know what to expect and can better anticipate how to structure when we upgrade and the testing I do on this end.
In general a release is considered beta until the next release is ready. If there is a majorly broken issue, (like 2.6.8 and 2.6.9) we'll pull it from availability instead. When the next release is ready, we will have the list of bugs found and fixed (there are almost never any outstanding issues when a release is made, with the exception of time_t rollover in 2036... still haven't figured that one out) which usually serves to mark the known issues of that release.
We try to have releases on a 2-3 month cycle. Sometimes it's sooner if there's a major new feature, or if there's a new platform that needs to be released.
Roland: wow... yes, you are absolutely correct about the bitwise or correction. That said, the nano's version is correct in this regard. Given that this version is now being deployed to both, the issue you raise is corrected.
