graham sanderson wrote:
Since this is my first bug to fix, I'm not very sure what the process is, but could someone help with setting the priority and targeting the 1.8 beta 2 release (if you agree), and give me any pointers on getting a quick review and maybe getting the issue into triage for 1.8?
You need to create a patch for the trunk (1.9) first and get it reviewed and checked in there, before it will be considered for 1.8. That said, it's unlikely that this bug will get accepted for 1.8 at this late stage. See posts in m.d.planning or http://developer.mozilla.org/devnews/index.php/2006/07/19/firefox-2gecko-181-approvals/
for more details about 1.8 planning. Neil _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
