Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[21924] Roadmap update #5412

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

[21924] Roadmap update #5412

wants to merge 2 commits into from

Conversation

MiguelCompany
Copy link
Member

@MiguelCompany MiguelCompany commented Nov 19, 2024

Description

This PR updates the roadmap cool ideas for future development of Fast DDS.

Contributor Checklist

  • Commit messages follow the project guidelines.
  • N/A: The code follows the style guidelines of this project.
  • N/A: Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
  • N/A: Any new/modified methods have been properly documented using Doxygen.
  • N/A: Any new configuration API has an equivalent XML API (with the corresponding XSD extension)
  • N/A: Changes are backport compatible: they do NOT break ABI nor change library core behavior.
  • N/A: Changes are API compatible.
  • N/A: New feature has been added to the versions.md file (if applicable).
  • N/A: New feature has been documented/Current behavior is correctly described in the documentation.
  • N/A: Applicable backports have been included in the description.

Reviewer Checklist

  • The PR has a milestone assigned.
  • The title and description correctly express the PR's purpose.
  • Check contributor checklist is correct.
  • If this is a critical bug fix, backports to the critical-only supported branches have been requested.
  • Check CI results: changes do not issue any warning.
  • Check CI results: failing tests are unrelated with the changes.

Signed-off-by: Miguel Company <[email protected]>
@MiguelCompany MiguelCompany added the skip-ci Automatically pass CI label Nov 19, 2024
@MiguelCompany MiguelCompany added this to the v3.2.0 milestone Nov 19, 2024
@Mario-DL
Copy link
Member

Cool additions.
It would be also interesting making PropertyPolicyQos mutable in the mid/long term, what do you think ?

@MiguelCompany
Copy link
Member Author

Cool additions. It would be also interesting making PropertyPolicyQos mutable in the mid/long term, what do you think ?

I think it is better to transform some/all of these into proper QoS.
We could then decide which of them should be mutable

Copy link
Member

@Mario-DL Mario-DL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@richiware
Copy link
Member

It would be great to have the ability to output statistics through a different interface than user data.

@richiware
Copy link
Member

Also I it would be great to have TypeAssignability

@richiware
Copy link
Member

Also configure ChainingTransport using XML (spoiler: already done in a custom branch)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-ci Automatically pass CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants