Stop requiring Status in package metadata; we now collect this information centrally
#5472
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Likewise for `CommunicatedBy` and `AcceptDate`. Motivation: this data logically does not belong with the package metadata controlled by package authors. Instead it should be stored in a central location managed by the GAP team.
wilfwilson
approved these changes
Jul 14, 2023
fingolfin
added
the
topic: packages
fingolfin
changed the title
Status in package metadataStatus in package metadata; we now collect this information centrally
fingolfin
added
the
release notes: use title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Likewise for
CommunicatedByandAcceptDate.Motivation: this data logically does not belong with the package metadata controlled by package authors. Instead it should be stored in a central location managed by the GAP team.
For example, in order to be accepted for distribution, currently GAP package authors must provide a proper release of their package, which then is reviewed. But that release should not yet have status
acceptedresp.deposited... so strictly speaking, right after the package is officially accepted, a second release with the updated status should be made right away.Indeed, for now the plan is to have this central location be in the GapWWW repository, see gap-system/GapWWW#330, simply because the website is the only place we need this data right now. We can of course change this in the future, but for now this way requires the least amount of work.