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

1.0.0 release #1873

Merged
merged 3 commits into from
Feb 21, 2022
Merged

1.0.0 release #1873

merged 3 commits into from
Feb 21, 2022

Conversation

jku
Copy link
Member

@jku jku commented Feb 18, 2022

This contains:

I think it makes sense to do the last two here and close the other PRs without merging -- the constant removal could be dropped as I mentioned.

I'm running release tests now, but review is welcome

@jku jku requested review from lukpueh and joshuagl February 18, 2022 12:16
@jku
Copy link
Member Author

jku commented Feb 18, 2022

force pushed to add my signed-off-bys to Lukas commits

@coveralls
Copy link

coveralls commented Feb 18, 2022

Pull Request Test Coverage Report for Build 1864618423

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

Details

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.2%) to 98.573%

Totals Coverage Status
Change from base Build 1852769022: 0.2%
Covered Lines: 1094
Relevant Lines: 1106

💛 - Coveralls

@@ -1,6 +1,6 @@
[metadata]
name = tuf
version = 0.20.0
version = 1.0.0
Copy link
Member

Choose a reason for hiding this comment

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

❤️

@lukpueh
Copy link
Member

lukpueh commented Feb 18, 2022

Nit: Mind squashing my two doc commits into one?

lukpueh and others added 3 commits February 18, 2022 15:23
Change docs in preparation of close v1.0.0 release.

- Remove important notice about upcoming 1.0.0 release from README
- Reword 1.0.0-ANNOUNCEMENT.md to not sound outdated after release

Co-authored-by: Joshua Lock <[email protected]>
Signed-off-by: Jussi Kukkonen <[email protected]>
Metadata API defines a specification version it supports already,
and that one is updated to the actual specification version we
produce.

Signed-off-by: Jussi Kukkonen <[email protected]>
* Update Changelog
* Update version numbers

Signed-off-by: Jussi Kukkonen <[email protected]>
@jku
Copy link
Member Author

jku commented Feb 18, 2022

force-pushed: no changes, but squashed a commit to one.

Copy link
Member

@lukpueh lukpueh left a comment

Choose a reason for hiding this comment

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

Just to make sure, are the following PRs not mentioned in the changelog on purpose, due to insignificance?

They were all merged after our last release 0.20.0

git log --oneline --merges v0.20.0..HEAD | egrep -o --color=never "Merge pull request #[0-9]+" | cut -d" " -f4

@jku
Copy link
Member Author

jku commented Feb 18, 2022

yes, looks correct -- I don't object to including them, they just seemed not relevant

Copy link
Member

@lukpueh lukpueh left a comment

Choose a reason for hiding this comment

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

🎉 Thanks for preparing the release, @jku!

Here's what I did to review: I checked that

  • the already approved #1869 is fully included in this PR,
  • all significant PRs are included in the changelog (see comment above),
  • all changelog items list the corresponding PRs,
  • and I proof-read the changelog

@jku
Copy link
Member Author

jku commented Feb 21, 2022

I'll have another quick look and will then get this done...

@jku jku marked this pull request as ready for review February 21, 2022 10:27
@jku jku merged commit 03d0232 into theupdateframework:develop Feb 21, 2022
@jku jku deleted the 1.0.0-release branch December 30, 2024 09:12
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.

Write 1.0 changelog / release notes Version 1.0 release strategy
3 participants