end-of-life to unmaintained?

[k-okada]

hi,
can I take over maintainer role of bfl as [email protected] ? if you give me access to this package, i'll change maintainer and status tag, and check if ros-infrastructure/ros_buildfarm#435 works.

[tfoote]

I've invited you to be a collaborator.

[k-okada]

Thank you, it seems you have already released into lunar, so we'll released from M

…

-- ◉ Kei Okada 2017-05-17 8:33 GMT+09:00 Tully Foote <[email protected]>:

I've added you as a collaborator. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAeG3Fg7zygrVF8Th48mjlE-JGUXDvgiks5r6jIygaJpZM4NaEFc> .

[tfoote]

From the discussion in #11 it likely won't need release into M turtle. It's only used by one other EOL package. It would be way better for the community to focus on phasing out robot_pose_ekf than rereleasing this package.

[jacknlliu]

It sounds a little sad. How many packages will leave with ROS in the future to powerful the world wide robots should be worthy of consideration.

[k-okada]

@jacknlliu if you plan to use this package in future, please let me know, we're happy to release in future ROS-distro

[dlaz]

people_tracking_filter also depends on bfl. If someone could do a release, that would be great, as I'd like to people_tracking_filter (and all of people) for melodic.

Is there something blocking bfl from getting into ubuntu main? I see debs are already being built: https://people.mech.kuleuven.be/~tdelaet/bfl_doc/installation_guide/node2.html

@DLu fyi

[k-okada]

@dlaz i think it is already released in indigo, kinetic and lunar https://github.com/ros-gbp/bfl-release

[dlaz]

Yes, but not melodic, which is what I'm interested in, or am I misunderstanding something?

[k-okada]

ok, done ros/rosdistro#17774

…

-- ◉ Kei Okada 2018-05-08 1:36 GMT+09:00 Dan Lazewatsky <[email protected]>:

Yes, but not melodic, which is what I'm interested in, or am I misunderstanding something? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAeG3FMb9L_ZljBnbMrex4YlTI2WpCNhks5twHgBgaJpZM4NaEFc> .

[dlaz]

Awesome, thank you.

[sloretz]

Since liborocos-bfl-dev is availabile in the Noetic target platforms Debian Buster and Ubuntu Focal, can this package be replaced with a rosdep key in Noetic?

• https://packages.debian.org/buster/liborocos-bfl-dev
• https://packages.ubuntu.com/focal/liborocos-bfl-dev

[k-okada]

@sloretz that's would be great. Did someone check if dependency package such as (http:https://wiki.ros.org/robot_pose_ekf?distro=melodic) works with liborocos-bfl-dev ?

[sloretz]

Did someone check if dependency package such as (http:https://wiki.ros.org/robot_pose_ekf?distro=melodic) works with liborocos-bfl-dev ?

@k-okada I just checked; robot_pose_ekf tests pass on Ubuntu Focal and Debian Buster using liborocos-bfl-dev

[sloretz]

ROS Noetic will use rosdep keys for BFL and KDL. The ROS Noetic migration notes has instructions.