Florian Forster

Hi @hnyman, that's an excellent question and I think we should have a community discussion about next steps and where we focus our energy. * `collectd-5.12` branch Historically, we have...

@mrunge What do you think?

Syncing *all* deviating changes is quite a tall order, given that `collectd-6.0` is ~250 commits behind `main`. I could try to just cherry pick all non-merge commits and see how...

If `collectd-5.13` has just two commits, I say we cherry-pick those into `main` and delete `collectd-5.13`. These merges over 200+ commits make the commit history incomprehensible. What are your feelings...

I looked into merging plugin changes from `main` to `collectd-6.0`. I looked at `src/*.c` as a proxy for plugins, though this list also contains unit tests, e.g. This is the...

I just merged the Perl CGI fix.

I created the [6 MVP](https://github.com/collectd/collectd/milestone/21) Milestone to track the things I think we need to get done before packaging our first collectd 6 release. Please take a look.

I started drafting a 6.0 release candidate at https://github.com/collectd/collectd/releases/edit/untagged-54315dd568937fe38d17

This is based on me grep'ing through the commit history to find PRs: ```sh git log --pretty=oneline "main..collectd-6.0" | egrep 'Merge pull request #([1-9][0-9]*)' ``` The PRs you mentioned have...

> PS. Of the significant fixes in v5 that should be added to v6 before any -rc release, I would propose at least your fix to missing `riemann_set_event()` terminators in...