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

docs: update news for 0.7.0 release #384

Merged
merged 3 commits into from
Nov 30, 2023
Merged

docs: update news for 0.7.0 release #384

merged 3 commits into from
Nov 30, 2023

Conversation

dshemetov
Copy link
Contributor

Since main is already on 0.7.0 and it's stable-enough, we should make it a release. This updates the NEWS with a few bullets from the release notes generated by the current main branch.

After we merge this, we can make a release 0.7.0, then bump the dev branch to 0.7.0.9000 (see Nat's comment in #383) and starting adding PR change lines under that heading.

@dshemetov dshemetov changed the base branch from dev to main November 30, 2023 20:39
Copy link
Contributor

@brookslogan brookslogan left a comment

Choose a reason for hiding this comment

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

Made some minor tweaks. 0.7.0.9999 in DESCRIPTION and NEWS.md from ds/clean will need updated to .9000 to match this or vice versa.

@brookslogan
Copy link
Contributor

That check failure's probably bad. Think we need a version range on epidatr.

@dshemetov
Copy link
Contributor Author

The check is failing because this doesn't have the ds/clean fixes in it, those are on dev.

@dshemetov dshemetov merged commit e7a4dfa into main Nov 30, 2023
0 of 2 checks passed
@dshemetov dshemetov deleted the ds/0.7.0 branch November 30, 2023 20:52
@brookslogan
Copy link
Contributor

Okay, 0.7.0 should actually include ds/clean then?

@brookslogan
Copy link
Contributor

sorry, I keep forgetting this didn't actually bump from 0.6.0.9999 or whatever to 0.7.0, just update the news retroactively.

@dshemetov
Copy link
Contributor Author

yea, doesn't seem worth trying to perfect 0.7.0. we should just try to get to a 0.8.0 release soon.

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