Right now, packages specify in their meta data whether they are accepted/deposited/submitted/... etc., and we don't really verify this. So in theory a package author could insert anything there.
It is also awkward that in order for a package to become accepted, it has to make a new release.
We should reconsider this. Logically, I don't think this state belongs into PackageInfo.g. Instead, I think we should store this data in a central place (e.g. in a JSON file in this repository, or whatnot). Moreover, I think the precise version of the package that was "accepted" should be recorded, not just the date of acceptance.
I've discussed this with Bettina Eick, and we'll discuss this further with the GAP council next time it meets, but in the meantime I wanted to record this idea here.
Right now, packages specify in their meta data whether they are accepted/deposited/submitted/... etc., and we don't really verify this. So in theory a package author could insert anything there.
It is also awkward that in order for a package to become accepted, it has to make a new release.
We should reconsider this. Logically, I don't think this state belongs into
PackageInfo.g. Instead, I think we should store this data in a central place (e.g. in a JSON file in this repository, or whatnot). Moreover, I think the precise version of the package that was "accepted" should be recorded, not just the date of acceptance.I've discussed this with Bettina Eick, and we'll discuss this further with the GAP council next time it meets, but in the meantime I wanted to record this idea here.