Release for ROS Jade?

Question

Release for ROS Jade?

davetcoleman opened this issue 8 years ago · comments

Package robotiq_ethercat depends on this package so cannot currently be installed on Jade from debian. Could someone release this package again? Thanks!

Shaun Edwards · Answer 1 · Fri Dec 23 2016 00:06:41 GMT+0800 (China Standard Time)

+1...We have some large changes in PR ros-industrial/robotiq#63 that I would like to pull into the jade development branch. The lack of a jade version of soem is holding things up. I'm happy to help out if needed.

Shaun Edwards · Answer 2 · Tue Jan 17 2017 12:57:34 GMT+0800 (China Standard Time)

Friendly ping.

Ruben Smits · Answer 3 · Tue Jan 17 2017 16:39:14 GMT+0800 (China Standard Time)

Would you mind if we skip Jade altogether and directly release kinetic? R.

On Tue, Jan 17, 2017 at 5:57 AM Shaun Edwards ***@***.***> wrote: Friendly ping. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAG0m4eLLyuzpY0G7JfvOO_3c5fbPVNvks5rTEo_gaJpZM4HdWml> .

-- Ruben Smits, Roboticist - Founder +32 479 511 786 Intermodalics - Gaston Geenslaan 9, 3001 Heverlee - BELGIUM www.intermodalics.eu

Shaun Edwards · Answer 4 · Wed Jan 18 2017 12:53:45 GMT+0800 (China Standard Time)

Jade is about to EOLed...Kinetic is definitely the priority.

Kei Okada · Answer 5 · Fri Jun 23 2017 17:11:05 GMT+0800 (China Standard Time)

hello, sorry to bother you, but can I ask you to release on kinetic?

If you think you do not have enough resource to maintain this package, could you consider give @k-okada and @7675t for write access to both this package and https://github.com/smits/soem-gbp
If you think you could not keep this package in your repository, Could you transfer these repository to https://github.com/ros-drivers and https://github.com/ros-gbp ? or can we host this repositories?

As I discussed in https://discourse.ros.org/t/releasing-repositories-form-other-people/1797/4 , I understand keep maintain the software is not a easy thing, and also it is not easy for others to take over the maintainership, because we, at least me, do not fully understand the source code of this package so it is hard for me to judege if incoming PR is correct or not, or cope with bug reportes and feture requests, but we still willing to use this software in new ROS distribution such as kinect.
What I proposed there is to create a group of maintainers (#10) who mainly responsible for releasing jobs, so that at least we can continue using the software in future.

Michael Görner · Answer 6 · Thu Jun 29 2017 20:10:46 GMT+0800 (China Standard Time)

We are waiting for a kinetic release over here as well. +1

Ruben Smits · Answer 7 · Thu Jun 29 2017 20:12:39 GMT+0800 (China Standard Time)

I should be able to do this quickly. If all goes well there should be a release pr on rosdistro tomorrow. R. Op do 29 jun. 2017 14:10 schreef Michael Görner <notifications@github.com>:

We are waiting for a kinetic release over here as well. +1 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAG0m7Q0F9rl0bVgyydPPs7r4GA5HhnNks5sI5RGgaJpZM4HdWml> .

-- Ruben Smits, Roboticist - Founder +32 479 511 786 Intermodalics - Gaston Geenslaan 9, 3001 Heverlee - BELGIUM www.intermodalics.eu

Ruben Smits · Answer 8 · Fri Jun 30 2017 17:03:01 GMT+0800 (China Standard Time)

@shaun-edwards @k-okada See ros/rosdistro#15414 I'm fine with moving soem and soem-gbp to ros-drivers and ros-gbp, I wonder if it would be easier to release directly the upstream https://github.com/OpenEtherCATsociety/SOEM instead of keeping this fork.

Dave Coleman · Answer 9 · Sat Jul 01 2017 01:20:24 GMT+0800 (China Standard Time)

What is the difference between this SOEM and the upstream version?

Kei Okada · Answer 10 · Sun Jul 02 2017 13:49:27 GMT+0800 (China Standard Time)

smits/soem has $Id: osal.c 416 2013-01-08 21:54:25Z smf.arthur $ (https://github.com/smits/soem/blob/master/osal/linux/osal.c#L17)
and OpenEtherCATsociety/SOEM 's inital commit was $Id: osal.c 464 2013-03-13 20:40:25Z smf.arthur $ (
https://github.com/OpenEtherCATsociety/SOEM/blob/7472dae1a275b103283147b923ea0c242a3e92fe/osal/linux/osal.c#L17)
so it should be between 1.2.8 and 1.3.0 https://github.com/OpenEtherCATsociety/SOEM/blob/7472dae1a275b103283147b923ea0c242a3e92fe/ChangeLog#L51-L80

At this moment, OpenEtherCATsociety have version v1.3.1 https://github.com/OpenEtherCATsociety/SOEM/blob/v1.3.1/osal/linux/osal.c and
we have more than 60 commit since then
OpenEtherCATsociety/SOEM@v1.3.1...master

Did someone using upstream version?

Kei Okada · Answer 11 · Sun Jul 02 2017 13:52:34 GMT+0800 (China Standard Time)

@smits thank you for your efforts, it seems you need to answer to ros/rosdistro#15414 (comment) to get them releasing.

Matthijs van der Burgh · Answer 12 · Sun Jul 02 2017 16:39:51 GMT+0800 (China Standard Time)

The differences between 1.3.0 and 1.3.1 are shown here: http://openethercatsociety.github.io/doc/soem/index.html

As mentioned in issue #9 , I tried using 1.3.1 myself. It did compile, but wasn't working at all. I think the main issue is the Added multi-threaded configuration for parallel configurations of slaves

Matthias Gruhler · Answer 13 · Fri Nov 30 2018 15:56:22 GMT+0800 (China Standard Time)

as kinetic has been released, I'll close this one.