T minus 3 days (one day in reserve for updates/regressions/checkins)

122 bugs left

5 bugs with patches and review? set.

Alright. T minus 7 days.
I filtered the list to stuff I actually
care about fixing, and think I can get done:

bug 166929 ChatZilla doesn’t have online/offline icon
bug 203264 “Hankaku kana” should be converted to zenkaku
bug 257728 Error: CEvent is not defined on /quit
bug 312931 Logging to the wrong view due to date changes.
bug 109993 Chatzilla scrolls with new input even when in scrollback
bug 293230 Do not copy “important” (stalk) messages to network tab when present and active in channel they occur in
bug 291723 Typing into a network view should say “Please do not type…
bug 278763 ChatZilla’s kick-ban command should put * at the end of a…
bug 317435 ability to drag nick from user list and drop into input area
bug 319628 Talkback-IDs should be clickable
bug 320103 In <prefs.js>, “Warning: reference to undefined property client.host”

Together with the bugs that already have review+ and those that still await review, I’m still giving myself a chance at making it . Of course, there is the problem of obtaining review in such a busy time of year, but we’ll see how that goes I suppose…

Edit: 123 bugs left. 4 with review? pending. Wooooooo!

As some of you may know, recently we (ChatZilla) are being screwed
by two bugs in Mozilla’s Core:

• Bug 319219 alias Bug 318419 alias Bug 291386: timers cause your commands and messages to get lost, or get you kicked off the server because we try and use ping / who / ison commands multiple times a second. Not like we want to, but since timers in Mozilla are somewhat broken of late…
• No bug filed yet. For some reason, Gecko thinks it’s funny to give some css rules line numbers like 18234154 – from a css file with less than a 1000 lines, that is. Of course, once it starts giving out random line numbers, the rules get applied in the wrong order, and the cz output document looks horrible. Yay. Of course, this screams ‘minimal testcase’ more than anything else, but here’s the catch(es):
  • No matter how hard we try, not everyone can reproduce this
  • There doesn’t seem to be any reliable pattern in when it screws up. It just does, at times
  • Even a ‘minimal’ testcase would still involve any amount of: a chrome xul document, with a <browser> with type=chrome, loading a chrome:// url html document, modifying that using the DOM to include a chrome:// url css file, which @imports another chrome:// url css file. We know for a fact that all these problems didn’t exist until we set the browser to type chrome to cope with other Firefox stuff (damn you, xpcnativewrappers). Why type=”chrome” and the CSS Parser can’t go through one door together, couldn’t tell you. I’d ask bz, but he’s on holiday for now, so we’re just screwed unless and until someone either figures out what causes this, makes a minimal testcase, or, heaven forbid, has steps to reproduce which mean everyone can actually see the bug…
    Edit: Now bug 321195

Sigh. So, Gecko, die.

Incidentally, as if this wasn’t enough yet, my exams suck, and I have no time to do work on CZ at the moment. I wonder if the ~8 days before new year will be enough. Time will tell

That’s right, at the end of October I set myself the goal of trying
to make sure there are < = 120 bugs on the ChatZilla open bug list before new year. At that point there were around 140 bugs left, so we were looking
at fixing around 30 bugs (given the fact that new ones are filed every now and then, too).

Right now the bug list has 132 bugs, and there are 6 open bugs
that are waiting for review, one waiting for checkin,
one other which might be checked in (has review, unclear whether we actually want a checkin)

So, we’re making good progress, and I hope we can pull it off by the end of the year. The only problem I’m seeing is that in 2 weeks,
I have a week to prepare for exams, and the next week I actually have the exams. Then the last one week of december, there’s obviously other
obligations for lots of us

PS: set your counters, 0.9.69 will be released off trunk on December 4th!

Edit: you may be
interested to know that here I have a list of the bugs I still want to fix before newyear (probably not going to succeed
in doing them all, but hopefully enough to make the target of 120 open ones before that time). Every week the list here changes with a semi-random pick out of that list that tells me what bugs I should work on. I don’t pick them
myself because, knowing me, I’d fix all the easy ones first and then fail to fix the medium/hard ones in the end .

Edit 2: patches for all the bugs for this week – and it’s only wednesday!

Edit 3: putting that up is just stupid, of course, since by now I need to do something else for one bug, so I’m not done yet