> I understand your frustration with a possible delay. But the feature is > glaringly broken, and in my mind it is worth fixing. I think holding > people accountable for knowing 100% of what needs to be done in an > onsite project is unrealistic at best, and doing so for a globally > diverse group of volunteers is even more dangerous.
I have to agree with this, this bug has been around and around, I don't have the time to do anything about it, Serge is offering to. If the code freeze was over this would not be a problem. If this had come up earlier it would also not be a problem. It simply isn't possible to manage the contributions people make, nor the timing of them, nor the participation people make in discussions. This bug is not on my personal radar because I have never used James with the filesystem, but can see why it is a showstopper for those who do, and having had it brought to my attention I can see why it should delay the release. Alternatively make the release and it can be fixed afterwards, there can be precious little left to do now. Please also note that your resistance to implementing mirroring have attracted the intervention of Greg Stein in his role as ASF chairman, something which I'm sure none of the longer serving commiters are particularly pleased about, and again if it were not for the drawn out release this could have been implemented prior or post the freeze. Therefore I'm prepared to -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
