it's been the topic of some debate and discussion. It's not realistic to keep the -devNN cadence we've set up and bring all of the supporting materials along completely in sync at each one, so then there's the question of where to balance it

one thought is that perhaps we shouldn't update any samples unless we completely rewrite them from spec each time; since the APIs are changing so much at the level of recommended idioms, it might result in samples that look like they've been run through google translate too many times if they're updated for mechanical API changes and not for structural recommendations

not sure we have any firm decisions yet

It still has FlexRow/FlexColumn so I guess not ?

In all cases, my point is: I understand it's a lot of work to maintain samples and codelabs while doing big API changes but kdoc should be automated and always up-to-date.