Kinetic release prep

[tfoote]

@wjwwood @mikeferguson is this what's needed for releasing bfl into kinetic?

[wjwwood]

I wouldn't duplicate the tracks.yaml entry, but the package.xml is ok.

[mikeferguson]

I honestly never remember how to release this package, and end up looking it up each time we have a new distro

[mikeferguson]

Do we also need to create a patches/kinetic branch?

[tfoote]

I was trying to duplicate the removed upstream import from herewhile adding new debian rules in the tracks.yaml I just fixed the references to the rosdistro.

@mikeferguson I think we're using the directtory overlay method instead of a branch

[wjwwood]

Is the upstream no longer there? Why do the import steps need to be removed?

I'm not sure copying the track.yaml entry is going to work. At the very least the release_inc should be reset to 0 or maybe removed (don't know which).

[mikeferguson]

Yes, the upstream is no longer there -- we ran into that during the jade release

[tfoote]

I reset the debinc number.

[tfoote]

@mikeferguson do you mind if I merge and try running bloom on it tonight?

[mikeferguson]

@tfoote, go right ahead -- I'm pretty sure last time around @wjwwood actually ended up making this repo work for me, so I really don't recall the steps involved