Skip to content
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

Freeze 1.6.0, introduce 1.7.0 (as dev) #415

Closed
wants to merge 3 commits into from

Conversation

braingram
Copy link
Contributor

@braingram braingram commented Dec 12, 2023

EDIT: this PR was too ambitious and has been simplified (removing the semantic versioning change) and now includes only the freezing of 1.6.0 and introduction of 1.7.0 (as the new development version).

I am leaving this as draft because the release of 1.6.0 will impact a large number of packages. A test PR is open for asdf where the downstream impact is being tested: asdf-format/asdf#1744

eslavich
eslavich previously approved these changes Jan 29, 2024
Copy link
Contributor

@eslavich eslavich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

.github/workflows/ci.yml Outdated Show resolved Hide resolved
@braingram braingram changed the title Use semantic versioning for extension manifests, introduce 1.7.0-dev Freeze 1.6.0, introduce 1.7.0 (as dev) Jan 30, 2024
@braingram braingram dismissed eslavich’s stale review January 30, 2024 19:31

Major changes were made to this PR and it is now not ready for review.

@braingram
Copy link
Contributor Author

@eslavich I dismissed your review here to not give the impression that the current state of this PR is approved. The current PR is quite different from the one you reviewed for a few reasons:

  • the change from non-semantic to semantic versioning should have been made in a new manifest extension schema
  • the release of 1.6.0 is causing a lot of package failures which should be reviewed before this PR can be re-reviewed

Thanks for giving this a look and I believe the above changes are still work doing (especially the new manifest extension schema). I just think they will require more extensive changes that will span multiple PRs.

@braingram
Copy link
Contributor Author

Superseded by: #422

@braingram braingram closed this Mar 28, 2024
@braingram braingram deleted the freeze_1p6p0 branch March 28, 2024 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants