Hi, At 11:34 21/02/2008, Amos Jeffries wrote:
You catch my meaning exactly. Great. I'm thinking some basic criteria in a 2-minute thought process along the lines of: Did it exist in 2.6 before 3.0? 2.7 before 3.1? - No => probably ignore. Is it just a patch-and-tweak (not a lot of work)? - No => oh well Is it a big change to existing code (_new_ code gets past this)? - Yes => oh well goodbye. Is it worth a few minutes my time? - No => oh well, goodbye. ** Okay, it _might_ be worth it. Spot-check core for vetos.
So, the next step is to define the list of the candidate changeset/bug, and assign them to someone.
Regards Guido - ======================================================== Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
