On Fri, Apr 13, 2012 at 12:34:59AM +0300, Felipe Contreras wrote: > Now what happens when: > > - you realize the fix made matters worst, in fact, so worst that the > whole thing is unusable in some systems > > Presumably we are now in the next round of: > > - fix upstream > > But v.3.3.2 is due Friday, which makes it very likely that the fix > won't get in. And what did we gain? If you simplify the situation to > what you explained above, it seems very reasonable, but that's not the > whole picture.
BTW, if you're so in need for critical fixes, why do you jump to the latest version ? It's known and accepted that stable versions stabilize over time with a few random hiccups during their early stage. You could have chosen 3.0 instead which generally holds some fixes that cooked longer before being merged. There's a cost at living on the bleeding edge. It's fun and sometimes it hurts but that should not be that dramatic that you spend so many emails telling how stable releases should be maintained. Willy _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
