Given that we are launching a MAJOR platform-wide user model upgrade - from buckets to collections - it is a shame (IMO) that our sample buckets are in the shape that they are currently in. The beer-sample is a total mess - still based on the now legacy bucket model, and showing the horrific ugliness of the _default mess that we're using to help transition legacy buckets. It should be changed to have two collections, beers and breweries, to show the new best practices! The travel-sample is a hybrid mess - it does have an upgrade to collections, but it also has an _default mess that should be eradicated. WHY? In my experience, folks look at samples as conveying implied best practices - and these are NOT best practices. Worst case if we have a need to have a legacy sample bucket as well, we should add one - but all of our longer term samples should now be showcasing collection-based best practices.
- relates to
MB-42726 Update `travel-sample` sample dataset bundled in the Beta software package
- links to