Robert Anderson

@tellthemachines, @SaxonF and I are actively working on this. I updated the issue to be an overview issue and added a few tasks that we've discussed. https://github.com/WordPress/gutenberg/pull/59052 added a new...

Update: A lot of this feature has involved synchronous back-and-forth chat so in an effort to make those conversations more transparent I've create [a channel in the w.org slack called...

Thanks for summarising everything in the issue description @SaxonF. I'll start digging into the four aspects described.

We definitely want to be able to export only submissions that are between some start and end date range.

Something that's been on my mind lately is how we have a lot of different APIs to do with restricting blocks: - The `templateLock` prop on `InnerBlocks` and `templateLock` block...

Definitely agree we should use API in https://github.com/WordPress/gutenberg/pull/46131 to `lock()` any new experimental APIs added between 6.1 and 6.2. I'd personally be on board with then considering all pre-6.2 experimental...

Thanks @ntsekouras. I edited the issue to bury the unimportant stuff in a ``. This is a much more manageable list. We should do it this way for future releases...

> * [ ] [__experimentalShowSelectedHint](https://github.com/WordPress/gutenberg/pull/44966) @noisysocks I've privatised this in https://github.com/WordPress/gutenberg/pull/47229. > * [ ] [__experimentalStyles](https://github.com/WordPress/gutenberg/pull/45960) @noisysocks I've stabilised this in https://github.com/WordPress/gutenberg/pull/47231.

The point of `lock()` and `unlock()` is that we want devs/extenders to not use it, right? In that sense I'd say no dev note is warranted.

> Rather than plugins having to do this manually, could core handle it for them? IE if a custom post type or taxonomy is `public` then it automatically becomes possible...