Hi,
>> From: Gerhard Froehlich [mailto:[EMAIL PROTECTED]] >> >I think that we already have this. It is the duty of the >> >committer to undertake initial quality control when they >> >accept the patch from Bugzilla and prepare for their >> >commit. If they do not know anything about the topic, then >> >they should not be taking on the patch - let someone else >> >do it. >> >> Who is someone else? Patches in bugzilla are very lonely in >> the moment. There are simply not applied. Why? Because there >> about 600 classes in Cocoon, about 10 active committers and >> nobody feels responsible. It's easy to say, oh I didn't >> wrote this code, therefor I can't apply this patch. But >> patches like NPE fixes, can be applied by every committer, I >> swear! > >Good point. Head is unstable so what do people think; have a >blitz and apply all the patches that can be? If a patch can't >be applied mark it as needing updated? Read the story of this bug. I applied this, even I didn't wrote the code and don't know in detail what's happing in the I18nTransformer. But Michael showed interest to make it better. The code was unstable at first, but now it's partly applied, stable (TIA Konstantin) and everybody learned something. <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7726> What happend: I applied -> uups buggy -> Konstantin got curious -> therefor Michael re-viewed his patch -> some recursions of the process ;-) -> partly applied and the party goes on But we're doing something, or? Greets Gerhard ------------------------------------------------------------------ Gerhard Fröhlich IBM Account Austria - 00/627 BIS e-business integration services IBM Austria / Vienna A-1020 Vienna, Obere Donaustrasse 95 Tel: ++43 1 21145 4818 Fax: ++43 1 21145 4191 e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
