need porting for Indigo release

Question

need porting for Indigo release

jack-oquin opened this issue 10 years ago · 8 comments

I ran a pre-release test, but it failed:

http://jenkins.ros.org/job/prerelease-indigo-freenect_stack/ARCH_PARAM=amd64,UBUNTU_PARAM=trusty,label=prerelease/1/

Looks like an incompatible change in the logging interface. I remember seeing similar problems with some packages in Hydro due to log4cxx includes being removed from some common ROS headers.

Answer 1 · 2014-05-16T18:52:28.000Z

I just discovered that the master branch is down-level. Apparently, we've been using hydro-devel as the default. That's annoying.

Answer 2 · 2014-05-16T19:39:43.000Z

I merged hydro-devel into master. That fixed the problem.

Answer 3 · 2014-05-16T19:46:00.000Z

released 0.3.2 to Indigo Igloo

Answer 4 · 2014-05-16T19:51:15.000Z

Deleted hydro-devel branch to avoid further confusion in the future.

Answer 5 · 2014-05-16T22:12:27.000Z

I believe master was being used by groovy, which is why it was separate from hydro-devel. My apologies for poor branch naming.

Unfortunately, the merge broke the groovy release: http://jenkins.ros.org/job/devel-groovy-freenect_stack/ARCH_PARAM=amd64,UBUNTU_PARAM=precise,label=devel/24/changes

We should create a new branch called groovy at this commit: b1a0f8a

Answer 6 · 2014-05-16T22:30:12.000Z

That's right. Sorry for breaking it. I'll fix it soon.

Answer 7 · 2014-05-16T22:46:25.000Z

We're not likely to make any more Groovy releases, so we don't really need a branch for it.

There's already a tag, so I'm just changing the rosdistro pointers for Groovy to use that.

Answer 8 · 2014-05-16T22:47:18.000Z

That seems like a reasonable solution. Thanks!