Central | Interface maintanence workflow is to cumbersome (#8)

[Sebastian Huber (@sebhub)]

Sebastian Huber created an issue: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/issues/8



The specification items in rtems-central provide a central point to define API level interfaces for RTEMS. They can be used to generate RTEMS sources and documentation sources. Lets suppose we want to update an existing interface item or create a new one, then we have to perform these steps:

1. Modify or create the specification items. Commit the changes.
2. Run `spec2modules.py`.
3. Go into `modules/rtems`.
4. Review the changes and create a patch set.
5. Open a MR (A) for `rtos/rtems` for the patch set.
6. Go into `modules/rtems-docs`.
7. Review the changes and create a patch set.
8. Open a MR (B) for `docs/rtems-docs` for the patch set.
9. Open a draft MR (C) for `prequal/rtems-central` for the specification item patch set.
10. Link (A) and (B) to (C) as dependencies.
11. Wait until (A) and (B) are merged.
12. Update the submodules `modules/rtems` and `modules/rtems-docs`.
13. Update (C) and remove draft state.
14. Wait for (C) review and integration.

In addition, some issue tickets may be required.

It would be a lot easier if there would be a single repository containing the RTEMS sources, the documentation, and the specification items.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/issues/8
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250908/457416ad/attachment-0001.htm>