On Wed, Nov 16, 2011 at 2:41 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote: > On Wed, Nov 16, 2011 at 2:35 PM, Ojan Vafai <ojan@chromium.org> wrote: > > Stated differently, I read it as saying the following: When we get to a > > state that some features are CR-ready and others are not, we should strip > > the non-CR-ready features and put them in the next version of that module > > and bring the CR-ready features to CR. > > That seems very different to me than marking individual features as > stable. > > Mainly, it's a ton of busy work. > > People keep saying that. It's really not. > > It's *more* work than just putting a note in a spec that says "hey, > this part is stable", sure. But it's not a huge deal. We have to do > the LC work to bring it to CR anyway, and making a new spec for the > next level isn't hard. Won't this mean we'll cut a new version as soon as any feature is stable enough to go unprefixed?
Received on Wednesday, 16 November 2011 22:57:11 UTC