On 05/07/2010 05:03 PM, Stephen Gallagher wrote:
As for this particular set of changes, I'm still going to resolve
particular issue in the way that Dmitri suggests for 1.2.0. That's
because this is a segfault and needs to be eliminated before we can ship
1.2.0 (the preview tarball of which is targeted to be released today).
So please understand that this is not me ignoring your patches, just me
opting to make a less-disruptive change at the end of a dev cycle. (And
also taking your advice about reducing code duplication)
I understand the situation and agree that a spot fix is the only option
for SSSD 1.2. I have already expressed this opinion before.
I just wondered how discovery of this nice booby traps in LDAP provider
code might affect your release schedule.