You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2023. It is now read-only.
We will need a versioning scheme for these schema. I'm punting on this for now to move forward, but it will need to be addressed before too long.
The changes here will be tightly coupled to those in pangeo-forge-orchestrator, which also doesn't have a versioning scheme, so perhaps these two will be linked in some way. Where that breaks down is that pangeo-forge-orchestrator will be updated much more than this repo, so perhaps they need to be versioned separately?
We're getting into a proliferation of versions here! Is there some way we can uniform/harmonize versioning across:
pangeo-forge-recipes
pangeo-forge-runner
meta-yaml-schema
pangeo-forge-orchestrator
?
How do other modular platforms manage this?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We will need a versioning scheme for these schema. I'm punting on this for now to move forward, but it will need to be addressed before too long.
The changes here will be tightly coupled to those in
pangeo-forge-orchestrator
, which also doesn't have a versioning scheme, so perhaps these two will be linked in some way. Where that breaks down is thatpangeo-forge-orchestrator
will be updated much more than this repo, so perhaps they need to be versioned separately?We're getting into a proliferation of versions here! Is there some way we can uniform/harmonize versioning across:
?
How do other modular platforms manage this?
The text was updated successfully, but these errors were encountered: