Jeffrey Novotny
Jeffrey Novotny
I noticed that we have a docs section on benchmarking. Do you think this information needs to be added to docs too? Or is it something that only developers/contributors would...
The content is basically ready for review with a few caveats: -- The API structure and links need to be finalized. Omnitrace uses a different structure than rocDecode and others,...
> I like the rewrite of the Post-Install. The ROCm docs split up their install and post-install sections to separate documents. Do you think we should, or is it short...
Closing and moving to a new branch
@tfalders Thanks again for the feedback. I've added your suggestions to the new commit and fixed up the merge conflict at the same time. It looks like a very old...
@AtlantaPepsi Are any docs updates required? I guess we will need a changelog entry too given that the changes will be apparent to customers.
@matyas-streamhpc Please let me know when it's ready for review. Looks like some edits (that were in the hidden ... click to expand section) are still outstanding. No rush if...
Cherry-pick to release/rocm-rel-6.3: Add metadata info and pointer to docs to the readme file (#193)
@cgmb Thanks for the approval. We're past RC1 now, so since this includes changes outside of the docs directory, I'd have to go through the release management cherry-pick approval. I...
Cherry-pick to release/rocm-rel-6.3: Add metadata info and pointer to docs to the readme file (#193)
@cgmb I believe the 6.3 release branch is open for a short time if you want to merge this. It's not high priority if it doesn't make it in.
Cherry-pick to release/rocm-rel-6.3: Add metadata info and pointer to docs to the readme file (#193)
No worries. We never received approval for this, but it's in 6.4, so we're good going forward. I forgot this was still open tbh.