Trunk Freezes for 1.3 Beta TonightTuesday January 21st, 2003The main development tree will freeze for Mozilla 1.3 Beta tonight at 11:59pm Pacific Standard Time. The freeze will remain in effect until 1.3 final is branched. During this time, only checkins that have been approved by drivers@mozilla.org will be allowed to land. The ideal release date for 1.3 Beta is Friday 24th January. Watch tinderbox for the latest tree status and consult the Roadmap for further information about the release schedule. Is it possible to search in bugzilla for bugs that have the "blocking1.3b+"? Go to http://bugzilla.mozilla.org/query.cgi and select "Flag / is equal to / blocking1.3b+" in the Advanced Querying Using Boolean Charts at the bottom of the page. well someone already posted the method, but for the lazy, the list is http://bugzilla.mozilla.org/buglist.cgi?product=Browser&product=MailNews&resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking1.3b%2B and the list of bugs waiting to be assessed (blocking1.3b?) is http://bugzilla.mozilla.org/request.cgi?action=queue&type=blocking1.3b not sure if it's in bugzilla, but i d/led openoffice 1.0.2 three times using moz, and the files were corrupted. then i tried with wget and got a good copy. At various times in the past, Mozilla has had problems automatically uncompressing files without telling you. For example, a .tar.gz file will be gunzipped, but will still keep the .tar.gz filename. These are usually easy to work around if you know to expect them. You can search Bugzilla for words like "download" and "corrupt" to find other bugs that might be causing this. If your download corruption doesn't match any of the bugs already filed, shut down Mozilla, get the latest nightly, create a new profile, and try again. If you can still reproduce the corruption, file a bug in bugzilla. It sounds like a lot of work, but it will only take about half an hour, and in the end you'll either understand your problem, or else you'll be helping get an important bug fixed. Good luck! There are problems with entering non-english text info some text fields. Look at bugs http://bugzilla.mozilla.org/show_bug.cgi?id=186798 http://bugzilla.mozilla.org/show_bug.cgi?id=188704 I think they are talking about the same problem and should be merged. Or there should be some RFE bug that is blocked by these two. January 24th. A couple of weeks early. Way to go, Mozilla community!! You are confused. What they are doing tonight is FREEZING the trunk for 1.3BETA (exactly as scheduled). The 1.3beta uideal release is on the 24th January but Mozilla has never relaeased a Milestone on the ideal date, shich is just that, ideal, NOT written on stone. Look at the Roadmap table located at http://www.mozilla.org/roadmap.html#tree-management Actually, I'm not "confused" at all. I was talking about how great it was that the trunk was frozen earlier than expected. Up until that time, we'd all been told that 1.3's release date was being pushed back to sometime in March because lots of things had been going on at the time. This latest news is an indication that the schedule is back on track. I didn't say that 1.3 was coming out on January 24. "trunk was frozen earlier than expected". no, it's right on schedule according to the roadmap. "we'd all been told that 1.3's release date was being pushed back". we had? who told you that? the dates were pushed back, in December, by a couple of weeks - 1.3b's release date to 24 Jan, and 1.3's date to 21 Feb - http://www.mozillazine.org/talkback.html?article=2787 this freeze is on time for the pushed-back schedule, nothing early about it... Somebody here posted a news item (a couple of weeks ago) saying that 1.3 had to be delayed. I forget who it was. In any case, they were able to make up the time & get back on schedule. It was delayed. Stevie Jobs and Safari had something to do with it, someone said. I don't remember who. In any case, Opera 7 is turning out fine for me. Glad to see we're back on track. Try it out! Yes, you are still confused about. Early in December Asa informed that 1.3B work was going to be extended 2 additional weeks to compensate for the lost time during the Xmas holidays. (in other words, that is old news and the decision was made public quite a while ago). The roadmap ALREADY reflected the time adjustment for the 1.3b freeze, as Asa informed all, and it has been posted like that for weeks now. I still don't get the fuzz about it. Version 1.3b freeze happened as scheduled, PERIOD. Chimera, Phoenix, Safari have nothing to do with it. What are the main improvements? Any speed improvements? thats the main thing cause everything else works nice bug 182997 - "showItem("context-copy") should check isTextSelected" http://bugzilla.mozilla.org/show_bug.cgi?id=182997 Got patch, waiting for reviews :/ Also there's this crasher bug when closing tab and then scrolling with mouse wheel, haven't checked wether it's know bug, but I surely hope so. Another bug that's getting on my nerves is 75866 - "Viewing message for very short time shouldn't mark it as read" http://bugzilla.mozilla.org/show_bug.cgi?id=75866 Also 157372 - "enhancement: multiple smtp/pop3 accs per set of folders" http://bugzilla.mozilla.org/show_bug.cgi?id=157372 And some lower priority things that should be fixed in the near future: http://bugzilla.mozilla.org/show_bug.cgi?id=43278 http://bugzilla.mozilla.org/show_bug.cgi?id=51683 http://bugzilla.mozilla.org/show_bug.cgi?id=69938 http://bugzilla.mozilla.org/show_bug.cgi?id=76831 http://bugzilla.mozilla.org/show_bug.cgi?id=86525 http://bugzilla.mozilla.org/show_bug.cgi?id=142729 http://bugzilla.mozilla.org/show_bug.cgi?id=159908 #15 enough features, long bugfixing period necessaryby weberjn Wednesday January 22nd, 2003 2:35 AM I find Mozilla has enough features, I don't miss anything (Really!). The only thing I miss is stability. I hate having to switch to IE because Mozialla crashes (unreproduceably). So I think there should be a feature freeze for half a year or so and only be bugfixing. At the moment there are 21910 new, assigned or reopened Bugs of Severity normal or higher in Bugzilla. #16 Re: enough features, long bugfixing period necessaby jsebrech Wednesday January 22nd, 2003 3:53 AM That's tough, but personal experience. I use mozilla 1.2.1 in both win2k and debian and I NEVER have it crash on me, unlike IE which has its odd moments of instability. Again, personal experience. I wonder what kind of configuration you run that makes mozilla so crashy for you. Personally, I miss a decent UI. Every single mozilla theme sucks. Modern doesn't fit in with anything and takes up too much screen real-estate, classic has really ugly icons (to the point of getting on my nerves), and they all share the trait of having too many menu's and a way too complicated preferences dialog (although I believe that last bit isn't part of the theme). Plus, all themes except for modern and classic lack polish (no offense to the theme writers, it's just a LOT of work creating a full theme). And when am I going to be able to split a tab into a new window, or change the order of tabs on the tab bar by dragging them around? Too bad phoenix is just a browser, or I'd use that (it's not ideal, but it's better). But I need the whole she-bang. So, I'd rather see more work going into the UI. But then that's selfish isn't it ;) Well, the number of open bugs in Bugzilla isn't a personal experience, is it ? ;-) ...then we end up in MozillaQuest territory. And we don't want to go there. The number of bugs reported is a sign of good testing, not poor stability. In any case, you counted the wrong figure: if you are considering stability, you should be searching only for crash bugs. Look for keyword 'crash' and select your OS plus 'all'; for Windows there are 388 right now, which is still a large number, but it's not thousands. Mozilla rarely crashes for me, either (well, except when I'm running dubious nightly builds). I mean it crashes less than IE, and I'm not saying IE crashes often either, that's also very rare. If you want real stability data you'd have to know the Talkback results. I have no idea what those look like. --sam Topcrashers for MozillaTrunk by build date for 10 days worth of Talkback data http://ftp.mozilla.org/pub/data/crash-data/Trunk-topcrashers.html Internet Explorer theme is nice and clean IMHO http://pages.prodigy.net/zzxc/ieskin/ and IE icon pack http://mozillako.hypermart.net/iconpacks/ plus some wicked tweaking for it http://kodu.neti.ee/~tar/mozilla.html For tabs wish there's: http://white.sakura.ne.jp/~piro/xul/_tabextensions.html.en For me there's ~118 bugs currently that if fixed would make Mozilla 99.99% perfect but that isn't going to happen in the near future and Mozilla still is awesome as it is, and getting better with every CVS commit :) bug 32157 http://bugzilla.mozilla.org/show_bug.cgi?id=32157 [RFE] Title tips (tooltips) for cropped text (probably the biggest UI *blooper* in mozilla) bug 91662 http://bugzilla.mozilla.org/show_bug.cgi?id=91662 Long strings in mail header cause scroll bars and attachment window to disappear, making message unviewable. (very visible bug - second biggest mozilla blooper) Bug 16489 http://bugzilla.mozilla.org/show_bug.cgi?id=16489 Password Protection of Profiles (much asked for by regular folk'. Has patch!) Bug 62429 http://bugzilla.mozilla.org/show_bug.cgi?id=62429 Replying with the "start my reply above the quoted text" pref on should prepend the signature above the quote text. (top) (Frequent corporate standard. Bearable if bug 141531 is fixed too) Bug 73567 http://bugzilla.mozilla.org/show_bug.cgi?id=73567 Ability to select from multiple signatures (global / per account?) (http://mozillapl.mozdev.org/ has a decent patch for this) Bug 155882 http://bugzilla.mozilla.org/show_bug.cgi?id=155882 Tasks (ToDo) need an Alarm (just like Events) (I actually use Tasks MUCH more than Events) Bug 177279 http://bugzilla.mozilla.org/show_bug.cgi?id=177279 Alarms don't fire under certain (very common) conditions (what good is a calendar if the alarms aren't reliable?) Bug 180029 http://bugzilla.mozilla.org/show_bug.cgi?id=180029 Running junk mail controls manually should respect preferences (This would consummate an already AWESOME feature) |