...
- When the call is closed, proposals for that call become frozen
- The freeze process generates a viewable form of the proposal which is no longer dependent on the schema (as an example, a PDF file) and this viewable form is stored with the proposal
- When backend changes are requested, an algorithm must be developed for converting the previous backend structure into the new backend structure. If no such conversion is possible (such as when a backend is removed), the algorithm simply removes usages of that backend
- As a result, copying an old proposal to make a new one is always like copying a proposal from the current semester, in terms of backends
- Backends that were dropped but used in old proposals are still visible in the frozen format of the proposal, just not in a machine-useful form
Performance Quality Attribute
SSA-6551 - Investigate responsiveness under high concurrency with Python web applicationsÂ