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

Update iceoryx release repository. #32073

Merged
merged 1 commit into from
Feb 8, 2022

Conversation

nuclearsandwich
Copy link
Member

This release repository was forked into ros2-gbp for the Galactic migration in April 2021 and has not been released into the upstream repository since.

Since the upcoming Rolling platform migration will again branch the release repository into ros2-gbp I recommend that we update it pre-emptively to reduce churn in the bloom configuration branches.

This release repository was forked into ros2-gbp for the Galactic
migration in April 2021 and has not been released into the upstream
repository since.

Since the upcoming Rolling platform migration will again branch the
release repository into ros2-gbp I recommend that we update it
pre-emptively to reduce churn in the bloom configuration branches.
@nuclearsandwich nuclearsandwich self-assigned this Feb 7, 2022
@nuclearsandwich
Copy link
Member Author

@dkroenke FYI

@github-actions github-actions bot added the rolling Issue/PR is for the ROS 2 Rolling distribution label Feb 7, 2022
@dkroenke
Copy link
Contributor

dkroenke commented Feb 8, 2022

@nuclearsandwich Thanks for the heads up!
We plan to update iceoryx for ROS 2 Humble to version 2.0, so we need access rights to https://github.com/ros2-gbp/iceoryx-release for bloom.
It would make sense that @elBoberido and @mossmaurice get access too for the case that one of us is not available.

CC @budrus @clalancette

@nuclearsandwich
Copy link
Member Author

We plan to update iceoryx for ROS 2 Humble to version 2.0, so we need access rights to ros2-gbp/iceoryx-release for bloom.
It would make sense that @elBoberido and @mossmaurice get access too for the case that one of us is not available.

I'm hoping to open a whole new tracker for release repository requests today alongside the Rolling transition to Ubuntu Jammy. Should the iceoryx release team be shared with the cyclonedds project or be separated from it?

Copy link
Contributor

@clalancette clalancette left a comment

Choose a reason for hiding this comment

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

Regardless of the changes required for the teams to have access, this can still go in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rolling Issue/PR is for the ROS 2 Rolling distribution
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants