-
Notifications
You must be signed in to change notification settings - Fork 97
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
Review and correct internal/ vs pkg/ code location #80
Comments
Need to move from pkg -> internal/pkg:
Need to tidy up:
Need to remove:
Candidates to move from internal/pkg -> pkg These are stable enough, but might not be interesting / valuable to make available.
|
As we are bumping to a new major version, we can remove pkg/ociruntime at this point. We don't have our own implementation of an OCI runtime since 3.10.0 and the code here is only used in e2e-tests. It's better to use the upstream oci runtime-spec structs / constants instead, in those tests. Part of #80
The sypgp package isn't really suitable for external consumption. Key handling / management, including sygpg, is intended to go through some refactoring in the near to mid future. Move to internal at this point, while we are at a major version bump. Part of #80
The required changes, from pkg -> internal/pkg, and removals, have been completed. Consideration of exposing stable parts of internal/pkg can be tackled when time permits. Adding functionality with breakage is okay in a minor semver bump. |
Type of issue
technical debt
Description of issue
Various portions of code in public pkg/ areas are not likely to be stable over time at present. This should be worked out so that it is possible to move toward the expectation that 3rd parties can use pkg/ functions with some stability, and as a stepping stone toward Go module semantic versioning conformance.
The text was updated successfully, but these errors were encountered: