New release/sync from master about config-rs HOT 5 CLOSED

Thanks for the response. The fix I'm looking for is in master, but I guess the PR would be porting it over to the release-013.x branch, which I do think would be pretty simple...but I guess the question is if that's worthwhile. It also makes me wonder what other fixes are in master that haven't been brought over, I suppose.

from config-rs.

Maintenance is very passive, that is true yes. But I am not against releasing a new version, I am just very conservative 😄 especially since some PRs have really long discussions on them and I fail to conclude them for myself 😢

from config-rs.

I think maintenance is rather low for config-rs lately.

• I have some PRs that I still need to wrap up myself (and hoping to finally have time for this month).
• I don't have the time to commit as a maintainer of the project myself, and it doesn't seem like there is anyone else coming forward to actively maintain the project.
• You'll possibly have to submit a PR with any changes you want into master. I imagine a new release will happen after my PRs are merged.

Alternatively, you may want to look into other crates with similar functionality that are more active in development / maintenance? (unless I'm mistaken with the current state of maintenance).

from config-rs.

Thanks @matthiasbeyer !

from config-rs.

Sure thing!

Just make sure to submit bug reports (or even better: Fixes) for everything you might hit! ❤️

from config-rs.