Consolidate the Kilted tables to be more compact and readable. #419
Conversation
christophebedard
left a comment
christophebedard
left a comment
There was a problem hiding this comment.
I think this is good. It could get tricky if we have different middleware versions for different platforms, but we can always have more *notes
As for OpenEmbedded, I don't have any strong thoughts about it, but I thought this was the intention for community-driven Tier 3 platforms?
Tier 3 platforms are those for which community reports indicate that the release is functional. The development team does not run the unit test suite or perform any other tests on platforms in Tier 3. Installation instructions should be available and up-to-date in order for a platform to be listed in this category. Community members may provide assistance with these platforms.
I guess it could go either way.
Signed-off-by: Chris Lalancette <[email protected]>
Signed-off-by: Chris Lalancette <[email protected]>
Signed-off-by: Chris Lalancette <[email protected]>
Signed-off-by: Chris Lalancette <[email protected]>
clalancette
force-pushed
the
clalancette/consolidate-tables
branch
from
4354d09 to
309296a
Compare
|
Based on @christophebedard's feedback, and the feedback from the ROS PMC, I've updated this now to include OpenEmbedded again. As I was going through this, I also noticed that the Middleware versions for both Fast-DDS and Zenoh were wrong, so those have been updated as well. I think this is ready for another review. If we are happy with this form, then I'll go back and do something similar for Jazzy and Humble. |
| " ** " means that the dependency may see multiple version changes, because the dependency uses a package manager that continually updates the dependency without a stable API. | ||
|
|
||
| " \*** " webOS OSE provides this different version. |
There was a problem hiding this comment.
were the ** and *** notes intentionally dropped?
| +-----------------+---------------------------------------------------------+-------------------------------------------+----------------------------------------------------------------+ | ||
| | | Tier 1 (Full Support) [d][a][s] | Tier 2 (Testing and CI Support) [d][a][s] | Tier 3 (Community Support) [s] | | ||
| +-----------------+------------------------------------+--------------------+-------------------------------------------+---------------+------------------------------+-----------------+ | ||
| | Package | Ubuntu Noble (24.04) (amd64/arm64) | Windows 10 (amd64) | RHEL 9 (amd64) | macOS (arm64) | Debian Bookworm (12) (amd64) | OpenEmbedded | |
There was a problem hiding this comment.
Looking at this table, Windows 10 falls under Tier 1 (Full Support) [d][a][s] now, but it previously was just Tier 1 [a][s], without the [d]. The way [d] and [a] are written, I don't think [d] applies to Windows 10: it has binaries available as a single archive (e.g., ros2-kilted-*-windows-release-amd64.zip), but no "Distribution-specific (Debian, RPM, etc.) packages."
| +--------------+------------------+---------------+------------------+-------------+-----------------+----------------+ | ||
| | arm64 | Tier 1 [d][a][s] | | | | Tier 3 [s] | Tier 3 [s] | | ||
| +--------------+------------------+---------------+------------------+-------------+-----------------+----------------+ | ||
| | arm32 | Tier 3 [s] | | | | Tier 3 [s] | Tier 3 [s] | |
There was a problem hiding this comment.
The Ubuntu Noble (24.04) arm32 Tier 3 [s] target platform isn't noted in the new table. Is this intentional? I know you mentioned you intentionally left things out during the PMC meeting yesterday; not sure if this was one of them.
Following on from #413 (comment), here is a draft version of consolidating the tables for Kilted. I think in this restructuring, we preserve all of the information, but present it in an easier-to-read and more compact format. Note that I intentionally left off OpenEmbedded here; we can add it back if we want, but it is a bit of an outlier because the ROS PMC doesn't maintain it (not even the documentation for it).
Thoughts about this? @tfoote @christophebedard