The only comment I have after a quick look over the changelogs is that usually we don't include a second level of bullet points in the changelog files.

The only comment I have after a quick look over the changelogs is that usually we don't include a second level of bullet points in the changelog files.

@gbiggs I am guessing that we didn't include a second level of bullets points because was not aware about important details in listed changes. And release preparation flow was to run a script, delete all second level bullet points which was actually message body from squashed merge commits.

Though I was the reviewer for every changes in this upcoming release and aware about some details and important changes which are not clear from one line in pull request title.
I decided to put a bit more details when it would be appropriate and nice to have for final user and added second level bullet items manually.

I've checked how it will be rendered. IMO it doesn't look weird or destructive. I found it to be very useful for final users.

@jhdcs I've addressed your comments about grammar.
Could you please verify and approve this PR?

@jhdcs @clalancette I am sorry, (I messed up a little bit) I realized that yesterday I merged #1053 on rolling/master. And now I need to rebase this PR with 0.17.0.
I have done rebase and updated changelogs with information about #1053 in 2179c96
I also temporary deleted tag 0.17.0 since it was assigned to the commit which is somewhere in the middle.
As far as I understand I will need to assign 0.17.0 tag on rolling directly right after I will squash and merge commits from this PR.

Please let me know if my assumptions and proposed actions are correct and I can proceed with merge and tagging.

@clalancette @jhdcs Since I didn't get any response in 24 hours. I am going to go ahead and merge this PR.

@clalancette @audrow I've tried to make release with bloom, however got error message about insufficient rights

bloom-release --rosdistro rolling rosbag2
ROS Distro index file associate with commit '0fa1904294ab891b243e231f14de8a995f3de3f9'
New ROS Distro index url: 'https://raw.githubusercontent.com/ros/rosdistro/0fa1904294ab891b243e231f14de8a995f3de3f9/index-v4.yaml'
==> Fetching 'rosbag2' repository from 'https://github.com/ros2-gbp/rosbag2-release.git'
Cloning into '/tmp/tmpwmey0xif'...
remote: Enumerating objects: 55104, done.
remote: Counting objects: 100% (4032/4032), done.
remote: Compressing objects: 100% (2947/2947), done.
remote: Total 55104 (delta 1181), reused 3676 (delta 944), pack-reused 51072
Receiving objects: 100% (55104/55104), 8.50 MiB | 6.60 MiB/s, done.
Resolving deltas: 100% (18329/18329), done.
==> Testing for push permission on release repository
==> git remote -v
origin	git@github.com:ros2-gbp/rosbag2-release.git (fetch)
origin	git@github.com:ros2-gbp/rosbag2-release.git (push)
==> git push --dry-run
ERROR: Permission to ros2-gbp/rosbag2-release.git denied to MichaelOrlov.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

It seems that I need to be in ros2-gbp/rosbag2 team to have permissions to push in those git repo.

I have created ros2-gbp/ros2-gbp-github-org#90 with request to join rosbag2 release team.