henry-fisher
commented
2 years ago Hey there! Yes, this is a massive limitation in our current workflow. Dates were never meant to be the longterm solution for this reason. We've been working on a new JSON format on the new repo which already utilizes version numbers. This will eventually enable us to keep track of the history of applications over time to see the changes. (New repo: https://github.com/techlore/Plexus-app)
I wanted to update the "eBay Kleinanzeigen" app (extreeeeemely popular in Germany) which has become virtually unusable with MicroG after v11.7.0 (current version is v13.9.0). How would I go about this?
If I enter a new testing date, the current format leads others to believe that on this same date, I tested the app without MicroG as well, which I didn't.
As of Feb 2021, the app has a rating of 3 and μ4. If the MicroG rating plummets to 1, do I simply deduce the other rating must be a 1 (at best)?.
I think just adding separate dates for tests with and without MicroG would solve this, + a note/hint to users that in cases where the MicroG rating is somehow lower, this in all likelihood means the (current version of the) app hasn't been fully vetted.
EDIT: Even better, use the release version instead of a date. People who use LineageOS et al. and who know how to handle Github in order to update the .csv probably also know where to find the version info of the respective app.