We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
#651 - Sync with upstream libraries (dependencies) and with API versions (ongoing)
We won't have time to re-do this for the final v11 release, and the third_party_code test (testSyncDates specificaly) is failing on them needing review again.
For now I put in a 3 year time between reviews so our continuous integration doesn't break down, but this needs reducing back to 1 year.
I prefer the plugin route as per my latest updates to MantisBT. Whenever possible, make a Composr plugin for the project to handle all the integrations instead of overwriting the projects' original code and having to maintain it.
There will be a couple of exceptions. For example, MantisBT still doesn't have full compatibility with our needs, so a few files still needed overwriting. And their sponsorship block (widget) is a disaster UI-wise, so I re-did it to conform to the layout of their other blocks (widgets).
I have retagged for v12 as we will need to revisit this regularly.
For now I put in a 3 year time between reviews so our continuous integration doesn't break down, but this needs reducing back to 1 year.
There will be a couple of exceptions. For example, MantisBT still doesn't have full compatibility with our needs, so a few files still needed overwriting. And their sponsorship block (widget) is a disaster UI-wise, so I re-did it to conform to the layout of their other blocks (widgets).