Giters

orocos / soem

ROS package wrapping the Simple Open EtherCAT Master (SOEM) from https://github.com/OpenEtherCATsociety/SOEM

Home Page:http://wiki.ros.org/soem

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Release for melodic?

mgruhler opened this issue · comments

commented

Are there any plans to release this for melodic in the near future?
Thx.

commented

Also asked on ROS answers.

@smits do you plan on releasing or are you abandoning this project?

commented

see also #10

commented

@smits I'd be happy to take this project over as maintainer, but I'd like to get your feedback/okay first. We've run into similar problems with trying to release a package that has been "hijacked" by someone else.

Also, in my experience, it makes sense to then transfer ownership instead of just creating a new repo or using a fork.

What do you think?

If we don't get any feedback, though, I'll try to go the "new repo" approach and like to make it as little intrusive as possible (new package name, etc), even though this will lead to another repo separation

commented
commented

@smits gerat. thanks. Could you also transfoer smits/soem-gbp?
Not quite sure if this is required, I'm not that much familiar with the ROS release process so far, but better safe then sorry.

Also, are you still depending on this, i.e. any future releases? Just that I know who to ping for tests when there are larger changes, that I plan on doing at some point. ;-)

commented

@mgruhler I'll do that. We are still depending on it, but the current state is good for us. Mind that there is an upstream repository at https://github.com/OpenEtherCATsociety/SOEM . The goal of this repo is mainly to be cmake and catkin compatible.

commented

Thanks. Totally clear.

I will not change anything for kinetic, as this is working okay for us as well. My short term goals are basically getting this released for melodic as is.

Further steps, though I'm not totally clear on timeline, required effort (and capacity ;-) ) and priorities yet, would be to

  • get around this header file madness in some more appropriate way :-)
  • see if we can use the latest release from upstream, ideally incorporate it (maybe using the submodule approach?)
  • or: clean this repo in terms of removing all not required files, i.e. windows/make file leftovers...

but those are just the ideas and I don't know how much time I'll be able to actually spend on implementation. But I'd like to at least be a contact point to release this into further ROS distros and maybe do some coordination.

So everybody reading this: any help is welcome ;-)

commented

FYI, I'll try to release to melodic within the next week