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 mrpt2 release repository. #32075

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

FYI @jlblancoc

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

Thanks for the ping @nuclearsandwich , but I'm afraid I missed the big picture :-)
Would it be better to delete the https://github.com/mrpt-ros2-pkg-release/mrpt2-release repo and release future versions directly to the ros2-gbp one? (would need write access, I guess?).

@nuclearsandwich
Copy link
Member Author

Would it be better to delete the https://github.com/mrpt-ros2-pkg-release/mrpt2-release repo and release future versions

It's probably not a good idea to delete the repository because people using older copies of the rosdistro repository may still try to find artifacts hosted there but you could archive that repository and stop using it.

Thanks for the ping @nuclearsandwich , but I'm afraid I missed the big picture :-)

In order to support the automation surrounding the Rolling distribution REP-2002 release repositories will need to be hosted in the ros2-gbp organization on GitHub. For repositories that aren't the migration tool will create an empty repository and push release artifacts for the migrated distribution to it. When we created the Galactic distribution from Rolling a release repository for ros2-gbp was created in this manner. As we get ready to migrate Rolling to Ubuntu 22.04 I'm doing some pro-active work to make sure that repositories which have been previously forked by the migration tool are synchronized with upstream so they don't get forked again, further bifurcating the release histories.

(would need write access, I guess?).

You are already a member of a team within the ros2-gbp organization with push access to the ros2-gbp/mrpt2-release repository so you should be able to make future releases using that releases repository without issues. If you do have any please let me know!

Copy link
Contributor

@jlblancoc jlblancoc left a comment

Choose a reason for hiding this comment

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

👍

@nuclearsandwich nuclearsandwich merged commit 9ac72d6 into master Feb 8, 2022
@nuclearsandwich nuclearsandwich deleted the nuclearsandwich/mrpt2-release branch February 8, 2022 15:45
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.

2 participants