Skip to content

Conversation

@ijnek
Copy link
Contributor

@ijnek ijnek commented Mar 28, 2022

Resolves: #2357

It would be great to address as many issues as we can while porting the documentation across.
I haven't tried out the new instructions yet.

Copy link
Collaborator

@kurshakuz kurshakuz left a comment

Choose a reason for hiding this comment

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

Thank you for starting this! As you mentioned that you have not tested it yet, I will just leave some high-level suggestions. Can you check the build status and fix the warnings on trailing whitespaces and missing newlines at end of files?
I would also suggest to make every sentence to be completely on a one line, this makes reviewing much easier.
Finally, I would like to leave the Minor differences from ROS 1 Bloom section somewhere, as it still may be useful for developers migrating to ROS 2.

@ijnek ijnek force-pushed the ijnek-bloom branch 2 times, most recently from e092295 to f256d67 Compare April 1, 2022 21:57
@ijnek
Copy link
Contributor Author

ijnek commented Apr 1, 2022

@kurshakuz
I appreciate the early review 👍

@dkroenke
Copy link

It hint to the package maintainer can be to ensure that a clean and up-to-date rosdep is available before releasing since bloom-release generates the package dependencies from rosdep.

@clalancette
Copy link
Contributor

It hint to the package maintainer can be to ensure that a clean and up-to-date rosdep is available before releasing since bloom-release generates the package dependencies from rosdep.

My understanding is that bloom ensures it is up-to-date (it always runs rosdep update during the release process). However, it does not currently detect whether you are using a custom rosdep database, which is where you could run into trouble.

@ijnek
Copy link
Contributor Author

ijnek commented Apr 25, 2022

FYI - I am still working on it but still requires time. It isn't ready to be reviewed yet.

@audrow
Copy link
Member

audrow commented Jul 25, 2022

It would be nice to have a checklist for keeping track of what has been ported or not (perhaps in #2357). Also, it would probably be easiest for us as reviewers if this was split into several smaller PRs, like one ported page, or one small but related group of pages.

@ijnek, thanks for taking on this large task!

@ijnek
Copy link
Contributor Author

ijnek commented Jul 27, 2022

@audrow Thanks for your suggestion, I agree that I'll have to break this up into multiple PRs for easier reviewing, I will start a checklist in #2357 per your suggestion.

@ijnek
Copy link
Contributor Author

ijnek commented Jul 28, 2022

@clalancette Thank you for reviewing so quickly!
I'm glad that most of the content was fine. I agreed with all of your points, and have made all the changes as necessary.

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.

All right, just a few more minor fixes, then this will be good to go.

Release-Track

**Releasing a package makes your package available on the public ROS 2 buildfarm.**
After you have created a package, this is the next step towards getting your package into the publicly available Debian packages!
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we can just remove this sentence now, as it is redundant with the next one.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This should be good now

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.

This is absolutely fantastic. Thanks again @ijnek for all of the work here, and the iteration. I'm going to go ahead and merge this, and also backport to the other distributions.

@clalancette clalancette added the backport-all backport at reviewers discretion; from rolling to all versions label Jul 29, 2022
@clalancette clalancette merged commit 90c48da into ros2:rolling Jul 29, 2022
mergify bot pushed a commit that referenced this pull request Jul 29, 2022
* Port across all of the bloom documentation from wiki.ros.org, updating it for ROS 2 in the process.

Signed-off-by: Kenji Brameld <[email protected]>
Co-authored-by: Chris Lalancette <[email protected]>
(cherry picked from commit 90c48da)
mergify bot pushed a commit that referenced this pull request Jul 29, 2022
* Port across all of the bloom documentation from wiki.ros.org, updating it for ROS 2 in the process.

Signed-off-by: Kenji Brameld <[email protected]>
Co-authored-by: Chris Lalancette <[email protected]>
(cherry picked from commit 90c48da)
mergify bot pushed a commit that referenced this pull request Jul 29, 2022
* Port across all of the bloom documentation from wiki.ros.org, updating it for ROS 2 in the process.

Signed-off-by: Kenji Brameld <[email protected]>
Co-authored-by: Chris Lalancette <[email protected]>
(cherry picked from commit 90c48da)
clalancette pushed a commit that referenced this pull request Jul 29, 2022
* Port across all of the bloom documentation from wiki.ros.org, updating it for ROS 2 in the process.

Signed-off-by: Kenji Brameld <[email protected]>
Co-authored-by: Chris Lalancette <[email protected]>
(cherry picked from commit 90c48da)

Co-authored-by: Kenji Brameld <[email protected]>
clalancette pushed a commit that referenced this pull request Jul 29, 2022
* Port across all of the bloom documentation from wiki.ros.org, updating it for ROS 2 in the process.

Signed-off-by: Kenji Brameld <[email protected]>
Co-authored-by: Chris Lalancette <[email protected]>
(cherry picked from commit 90c48da)

Co-authored-by: Kenji Brameld <[email protected]>
clalancette pushed a commit that referenced this pull request Jul 29, 2022
* Port across all of the bloom documentation from wiki.ros.org, updating it for ROS 2 in the process.

Signed-off-by: Kenji Brameld <[email protected]>
Co-authored-by: Chris Lalancette <[email protected]>
(cherry picked from commit 90c48da)

Co-authored-by: Kenji Brameld <[email protected]>
@ijnek ijnek deleted the ijnek-bloom branch July 29, 2022 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-all backport at reviewers discretion; from rolling to all versions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Porting Bloom documentation to ROS2

5 participants