[backlog table] Update as of 19/03

[albertoramosmonagas]

What type of PR is this?

• documentation
• subproject management

Summary:

• Application Profile approval requirement added (API enhancement).
• Corrected Fraud Prevention submission date (sent on February 20th with Device Management)
• Updated Network Health and Traffic submission dates (Network Health: March 6th).
• Corrected Device Management submission date (sent with IoT Fraud Prevention).
• Added Steering of Roaming Management entry.
• Fixed QoS Booking repository and maintainers assignment (previously reversed).
• IoT SIM Status Management was missing from the table—now included.
• Updated Dynamic Data entry with the new name.
• Replaced IoT Network Optimization Template with IoT Data Transfer (swapped).
• Removed two Voice APIs from "Sent To TSC" (now marked as pending).
• Added Identity and Consent Management to the backlog table for Cellcard.

What this PR does / why we need it:
Including status changes on #24, #167, #73, #95, #30, #67, #164, #144, #128, #127, #35

[caubut-charter]

Thank you for the submission. A few items before merging:

• It looks like you may need to merge main into your branch as this PR reverts some previously fixed entries.
• Some of the formatting on the tags aren't aligned with the rest of the document.
• The basic shape of a row is also a little different from the rest of the document. For instance, the Maintainer links aren't wrapped in divs.

I only commented directly on a few occurrences, but it looks like most additions will need to be adjusted.

[hdamker]

Please merge this PR as soon as possible (I would recommend to have only short-running PRs for these updates, to avoid that the PR is already outdated when it gets reviews).
Afterwards I propose to decide to either reflect the Spring25 releases or to reduce the information in the last column (e.g. to the first release, or a link to /releases in the repository as soon they have one etc).

We have the release information already:

• within the GitHub repositories (source of truth)
• within the wiki in the release trackers and on the Meta-release pages
• as an overview on https://github.com/camaraproject
• on the API description pages on the CAMARA website

With that the added value of concrete release information within the APIBacklog table might be limited.

[albertoramosmonagas]

• on the API description pages on the CAMARA website

Hi @hdamker,

I totally agree, we should merge this PR as soon as possible. What you propose to reflect the spring25 or reduce the information in the last column I don't have a strong opinion about that because although the information is accessible in many places, not everyone accesses by the same ways depending on the role they have in the organization, so I don't see bad to have it here either, but we can scale it as an Action Point in the next TSC (@jgarciahospital)

Continuing with the point of merge this PR, all the requested changes are already committed, but I don't have permissions to merge it, if you could approve the code and close this issue.

[hdamker]

but I don't have permissions to merge it, if you could approve the code and close this issue.

My approval wouldn't unblock the PR as I'm not a codeowner here, you need one codeowner review and approval. Best would be if @caubut-charter confirms with an approval that his requested changes are done, otherwise you would need to dismiss this review before you can merge.

[jgarciahospital]

LGTM

[caubut-charter]

Small formatting changes.

[caubut-charter]

Couple more. Will do a quick visual test as it looks like some rows have a different number of columns at a glance.

[caubut-charter]

Few more from visual inspection.

[caubut-charter]

LGTM

[hdamker]

@caubut-charter the changes are looking good, but it's actually a loop-hole that you are able to approve and merge as a co-author and after making the last changes (YOLO ... you love it you merge it 😉).

[caubut-charter]

@hdamker I was wondering why I was allowed. I know GitLab has a setting to disable approving if you add commits, not sure about GitHub.