On Fri, 2011-01-28 at 11:03 -0500, Francis Giraldeau wrote: > I used augeas python bindings in the past, but they were not up to > date with the latest API. Recently on IRC, someone reported an > incompatibility between ruby binding version and augeas version in his > distro. > > To avoid this situation, I would propose to make a release candidate > say two weeks before the official release, to allow some time to > bindings folks to test and update and release their projects. > > Does such a process would be feasible without too much overhead? Is > there a better way to handle this?
I think we don't need a formal release candidate - but maybe a nag to bindings maintainers just before and after a release to update things. I know I've dropped the ball on the Ruby bindings somehwat. For all the other bindings, who is still actively maintaining them ? David _______________________________________________ augeas-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/augeas-devel
