At the moment users need to wait for the next atmo release to try a new emr version in the best case. Someone also needs to write a patch and generate a new db migration. We could instead create a new db model with its counterpart in the admin site. That would make adding/removing a emr release as easy as clicking a button.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.