Create separate profile PDF for each profile family release (e.g., RVA23) not one PDF for all profiles in a family (e.g., RVA)

[james-ball-qualcomm]

Appendices (e.g., instructions, CSRs) are a function of the profile family release each release needs to have its own PDF.

[mipsrobert]

As both RVA23 and RVB23 are recently ratified, should not database be updated to reflect ratified specs?
I only see RVA, but not RVB.

[james-ball-qualcomm]

Yes, that is the plan. From: Robert Chyla (MIPS) ***@***.***> Sent: Monday, November 4, 2024 11:06 AM To: riscv-software-src/riscv-unified-db ***@***.***> Cc: James Ball (QUIC) ***@***.***>; Assign ***@***.***> Subject: Re: [riscv-software-src/riscv-unified-db] Create separate profile PDF for each profile family release (e.g., RVA23) not one PDF for all profiles in a family (e.g., RVA) (Issue #237) WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. As both RVA23 and RVB23 are recently ratified, should not database be updated to reflect ratified specs? I only see RVA, but not RVB. — Reply to this email directly, view it on GitHub<#237 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBRBTGGEL6SL6SJ6UJ5T72DZ66ZQXAVCNFSM6AAAAABRBHZVCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJVGQ4DQNZWGQ>. You are receiving this because you were assigned.Message ID: ***@***.******@***.***>>

[james-ball-qualcomm]

PR #249 fixed this.