-
-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing required #7027
Comments
For reference, this was the original feature request: KSP-CKAN/CKAN#904 One possible test case is xScience → xScienceContinued in #7021. |
Expand for the (very long) list of identifiers in NetKAN that might be applicable...
|
How will old (1.25) clients react to metadata with a higher (1.26) spec_version? Is it safe to merge #7048? |
Maybe I'm just a noob, but: Is it a little confusing that |
If this was all being designed from scratch, then yes something like |
OK, a repo update that contains a future spec version will throw However, that will then be caught by the repo update code, which just skips the module: So we won't cause crashes by merging these, but clients older than the 1.26 prerelease will see some module versions disappear upon a repo update. I guess that's a necessary evil to get the testing done. |
CKAN v1.26 is out in the wild; presumably the testing was done. |
@KSP-CKAN/wranglers, there's a new pre-release available that includes the long-delayed "replaced_by" addition to the spec. (Huge thanks to @HebaruSan for finishing up the code that had me dithering about implementation specifics!)
We really need some of the old entries in CKAN-Meta modified to use the new field so we can test out the new client.
The text was updated successfully, but these errors were encountered: