search

start-jsk / openhrp3

This package does not only wrap OpenHRP3 but actually provides the built artifact from the code from its mainstream repository. Being ROS-agnostic by itself, you can also use this via ROS together with the packages in rtmros_common that bridge between two framework.
1 stars 5 forks source link

Release 3.1.5-6 #43

Closed 130s closed 10 years ago

130s commented 10 years ago

Waiting for https://github.com/start-jsk/openrtm_aist_core/issues/49 to be done.

130s commented 10 years ago

Now ready to be released. Pre-release job.

130s commented 10 years ago

Pre-release test was unstable probably because some failures occurred in downstream. As similar to what I reported here, it's hard to tell from these failures if there's an issue within the package tested or not because some unit tests in downstream themselves are not stable.

That said I'll release this now.

130s commented 10 years ago

Submitted.

130s commented 10 years ago

Do Groovy users also need this to be released? Personally because there's a critical error that is blocking OSRF's entire Groovy sync, I'm hesitating to make new release into G, at least for now.

k-okada commented 10 years ago

It does not needed but It always better to release them, but I understand your situation so I'll working on releasing into groovy until it becomes stable.

130s commented 10 years ago

Let me be clear; I'm afraid adding new release might increase the risk of breaking the build. So I prefer to prioritizing making the buildfarm stable for Groovy.

k-okada commented 10 years ago

As I wrote on https://github.com/start-jsk/rtmros_common/issues/410#issuecomment-40468868, I suppose current situation is not because of groovy, but rmtros_comon itself is not enough stable. so even if we stop releasing on Groovy, it will break if we release on Hydro/Indigo and same bug fix will works for both releases.

By the way, how do we cope with https://github.com/start-jsk/hrpsys/issues/75, they want to start using trunk version of hrpsys.

One idea is to create groovy branch on rtmros_common and stop developing/releasing and using hrpsys 315.1.x and hydro branch is continue developing on trunk (315.2.x), but this means hironx users must use groovy, so it may not acceptable.

Another idea is to create stable(315.1.x) branch on rtmros_common and only stable branch is released and deb build. This means main/core users never uses deb package. Also I afraid I mostly working on developing release so it just make you much more busy.

Another approach is to release rtmros_common and rtmros_comon_devel ?

Ideal approach is to update QNX software to 315.2.x but it may most difficult among above idea.

130s commented 10 years ago

Let us continue at https://github.com/start-jsk/hrpsys/issues/76