Make new release

[agoode]

We want a new release to pick up the new heuristic behavior.

[Neustradamus]

@agoode: Yes and it will be good to move here to have a better devel:

• https://github.com/avahi

cc: @lathiat.

[yomach]

Hi,
Any plans for this release? It's been 9 months since the PR was merged, and it's a small fix...

[Neustradamus]

Currently, there are 2 PRs:

• Use libtool's -version-info feature for library versioning #74
• Mdns minimal mode #89

And a lot of issues:

• https://github.com/lathiat/nss-mdns/issues

But a new build is needed...

[Neustradamus]

Dear nss-mdns team, @lathiat, @agoode, @poettering,

I have done a ticket about the progress of the transfer of this avahi repository (https://github.com/lathiat/avahi) and nss-mdns repository (https://github.com/lathiat/nss-mdns) to avahi GitHub organization that I have created to have a best future, a best development, new releases?
Note: I have not rights now.

It is here:

• Transfer this repository to avahi GitHub organization #92

I think that @agoode must to be in the avahi GitHub organization (if it is not yet).

Badly, at this time, a lot of people think that it is a dead project like Avahi and maybe unsecure like Avahi.

• Make new release #85
• New version, 0.9 ? avahi#325
• is there a plan for v0.9 tag? avahi#430
• New release to fix all CVEs since 2021? avahi#503

Some projects have been blocked at an old place because the "original" repository can not be transfered because a death, away dev, ...

For example:

• https://github.com/glennrp

Thanks in advance.

[Neustradamus]

Currently, no new build has been released since 0.15.1 (2021-06-12), more 3 years...

[Neustradamus]

@agoode: Have you stopped to work on nss-mdns?

[agoode]

Yes, I have moved off of this project.

[arrowd]

Maybe some of avahi/avahi developers will pick up the banner?

[pemensik]

Maybe more people would commit their time to avahi project, we certainly need more people contributing. While we have pending issues blocking avahi release, I think we do not have any blocker here with nss-mdns plugin. I think we can release it as it is and maybe release new version again. They do not need to be strictly bound to avahi releases itself.

[evverx]

They do not need to be strictly bound to avahi releases itself

I think if changes in avahi affect nss-mdns and nss-mdns itself is changed to match avahi it makes sense to release them together. For example avahi can now resolve all the valid names and send them via the avahi-daemon socket (nss-mdns hasn't been changed though (it reads only 256 characters)). Then again it mostly affects hostnames with long unicode names (and has never been reported here) so it's probably safe to say it can be changed and released in nss-mdns separately later .