2 questions regarding thirdparty release.

Q-1. For making a new release into a new ROS distro, following Releasing a Third Party Package On a release repo local directory at master branch, I ran the following and got an error. And maybe because of this error he subsequent command fails as follows.

$ git-bloom-release kinetic
+++ Cloning working copy for safety
Processing release track settings for 'kinetic'
What version are you releasing (version should normally be MAJOR.MINOR.PATCH)? 1.0.3

Executing release track 'kinetic'
==> bloom-export-upstream https://github.com/AndreaCensi/csm.git git --tag 80f15ff601fdc599995e7d963e4c1b4c3c72f897 --display-uri https://github.com/AndreaCensi/csm.git --name upstream --output-dir /tmp/tmp3KKCch
Checking out repository at 'https://github.com/AndreaCensi/csm.git' to reference '80f15ff601fdc599995e7d963e4c1b4c3c72f897'.
Cloning into '/tmp/_tCMyU/upstream'...
remote: Counting objects: 5364, done.
remote: Total 5364 (delta 0), reused 0 (delta 0), pack-reused 5364
Receiving objects: 100% (5364/5364), 3.49 MiB | 980.00 KiB/s, done.
Resolving deltas: 100% (2808/2808), done.
Checking connectivity... done.
Exporting to archive: '/tmp/tmp3KKCch/upstream-80f15ff601fdc599995e7d963e4c1b4c3c72f897.tar.gz'
md5: f9306214c6b948dc77eb63a5c1886183

==> git-bloom-import-upstream /tmp/tmp3KKCch/upstream-80f15ff601fdc599995e7d963e4c1b4c3c72f897.tar.gz kinetic --release-version 1.0.3 --replace
Given patches path 'kinetic' does not exist in bloom branch.
<== Error running command '['/usr/bin/git-bloom-import-upstream', '/tmp/tmp3KKCch/upstream-80f15ff601fdc599995e7d963e4c1b4c3c72f897.tar.gz', 'kinetic', '--release-version', '1.0.3', '--replace']'

$ git checkout release/kinetic/csm
error: pathspec 'release/kinetic/csm' did not match any file(s) known to git.

Q-2. For an update release to a older ROS distro, future releases section in Releasing a Third Party Package page simply "redirects" to a Releasing a catkin Package page, which seems generic instruction for non-thirdparty package release that I think just can't follow from the beginning of the page.

At a loss, I just ran the following command for my thirdparty package:

bloom-release csm --track jade --rosdistro jade

But this only picks up the older commit from the upstream repo and doesn't pick the newer commit that I want. I assume Relaease Tag is where I specify the commit to pick, but it's not clear how to update it for the 2nd+ time release.

So what's the right way for 2nd+ time release?

(I have to admit that the thirdparty release instruction is very difficult for me...although I've tried to understand many times hoping that once I get a better understanding I can contribute to editing it...)