Gareth Bowen

We bump dependencies (almost) every minor release, so I'll add this to 3.12.0 to be done at the same time.

Related: #5903

Deprioritised out of this release.

Update on this - instead of a single config, we should have a single config per suite.

Scheduling for 4.0.0 because that's the ideal time to do any data migrations that may be necessary for this.

@dianabarsan assures me that we can reverse engineer from JSON to XML so we should just do that.

Yes, I should have updated this issue so it now only covers step 1. We've decided not to run any major migrations in 4.0.0 so step 2 will have to...

It depends on the implementation, because we may need to store more information to completely reproduce the xml, but in all likelihood it's not a breaking change.

We're getting towards the end of the dev cycle on 3.11.0 and I'm trying to keep it lean to get the release out ASAP. It's possible that this bug will...

@latin-panda Sounds good! If it makes sense it may also be something we could contribute back to enketo-core but it depends how generic the solution is.