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

Release r1.1 (Release Candidate) #71

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

PedroDiez
Copy link
Collaborator

What type of PR is this?

  • documentation
  • subproject management

What this PR does / why we need it:

Blockchain Public Address Release r1.1 (Release Candidate) PR (Spring25)

Which issue(s) this PR fixes:

Fixes #66
Fixes #63
Fixes #65
Fixes #64

Special notes for reviewers:

The following PRs MUST be merged prior to this one:

Update User Stories filename in #67
API Spec aligment with Commonalities and ICM in #69
Basic Test cases definition in #70
Generate API Readiness Checklist in #68

Changelog input

Release r1.1 (Release Candidate) for Blockchain Public Address API

Additional documentation

This section can be blank.

docs

@PedroDiez PedroDiez self-assigned this Jan 15, 2025
@PedroDiez PedroDiez added documentation Improvements or additions to documentation subproject management Indicating issues with subproject repository or release management process labels Jan 15, 2025
@PedroDiez PedroDiez requested review from rartych and a team January 15, 2025 16:38
@hdamker
Copy link
Contributor

hdamker commented Jan 15, 2025

Hi @PedroDiez thanks for creating the release PR. I've created for the review camaraproject/ReleaseManagement#138, but seems we need to wait until the open PRs are merged.

The release PR

  • touches also the YAML file(s), checklist, test definitions and set the right version numbers in all files
  • the checklist could have been part of the release PR, as it describes the status of the repository at time of the release. A separate PR isn't necessary for that

Minor point:

@PedroDiez
Copy link
Collaborator Author

Hi @hdamker,

Thanks for the comments.

  • Understood about API Readiness Checklist (will do in that way in the next releases)
  • Have also addressed the README.md removal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation subproject management Indicating issues with subproject repository or release management process
Projects
None yet
3 participants