Release request

[jlack1987]

Are there plans to put out a new release soon by chance? Looks like it's been almost a year since a new release here and there have been some good updates/fixes in the mean time 😄

[henrygerardmoore]

Yes, that's a good idea; I'll try to do one soon.

[jlack1987]

Hate to be a bother, but any chance there's a release planned soon? I've got downstream changes I can't release until this gets released unfortunately because I relay on the fixes here

[henrygerardmoore]

@nbbrooks any chance I can get maintainer status for this repo? @jlack1987 not a bother at all, but I am no longer at PickNik and I think I'll need to be able to merge things to be able to follow the bloom release process

Edit: alternatively, Nathan you could just do the data tamer release if you'd prefer that

[nbbrooks]

@henrygerardmoore I sent you maintainer access - looks like you are already on the release team https://github.com/ros2-gbp/ros2-gbp-github-org/blob/latest/data_tamer.tf

I am also slogging through a backlog of releases, I may get to it before you (I'll tag you if I do)

[jlack1987]

I'm i'm reading things correctly it looks like this latest version(1.0.3) was released for kilted and rolling but not jazzy. Any chance you could do a jazzy release?

[nbbrooks]

@jlack1987 I'm working on a 1.0.4 release for kilted, lyrical and [resolute] rolling. Unfortunately v1 of data_tamer was released after Jazzy's initial release and it does have some breaking changes:

• Custom types refactor (custom_types.hpp, LogChannel::registerCustomValue signature)
• LoggedValue<T> API rework (new logged_value.hpp header, changed lock semantics via locked_reference.hpp)
• Ros2PublisherSink gained lifecycle-node support, with constructor becoming a template
• channel.hpp reshape

This is why Jazzy and earlier are still on < v1. There should not be anything keeping you from migrating to the v1 API with a source build of main on Jazzy though.

If you are simply looking for a buildfarm release of the 0.9.4 API but with additional bug fixes, e.g. 0.9.5 (but none of the breaking changes in v1) let me know and I can look into that.

[jlack1987]

Hey @nbbrooks appreciate the context there. I'm not sure of the specific version number but its the commits from this PR that helps ensure we can flush any buffers and properly finish mcap logging on destruction.

[nbbrooks]

@jlack1987 could you test if nbbrooks/v0.9-backports contains the functionality/bug fixes you need before I cut the releases?

[jlack1987]

Ty @nbbrooks I gave it a shot and as we have been running against main I realize we have also been using updates from #68 as well. I think those should be safe to backport as well