Concern has been raised over the timing of the landing of the patch to remove most uses of the casting macros macros from the tree, so I'm addressing it in a new top-level post, CCed to the most-affected newsgroups by source code changes. (Was m.d.t.dom right for content/? I'm unsure.)
I will land the changes this Saturday night, PDT. I will delay to the gecko meeting for scheduling if active layout/content hackers (the people most affected by removal of the casting macros, with nearly a third of all modified files), or a "reasonable" number of other developers who will be affected by this, request it. If they do not, I will not delay. If only a few modules request a different landing time, I will omit directories individually, but I hope not to do so. Merging work-in-progress with this will suck, but it will suck now as much as it will suck later. Every day now is a day later in the cycle, and landing a big change early, when people have the longest time to adjust, is the right thing to do. This will be delayed only if sufficient core hackers will be affected by it, but those hackers must speak their concerns to affect the time table; I will not defer to shadows. By Saturday night they'll have had nearly a week to do so during the busy-ness of the very start of the b1 cycle, when development is most active; I think that's entirely adequate. Jeff _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
