Slashdot Mirror

Yes, somebody has taken a stab at the date. Accodring to the manifesto, we will see a few more releases (0.9.6-0.9.9) followed by 1.0 or 0.9.10 then 1.0. there will be NO other milestones. The document claims we have about half a year until the 1.0 release. This is the first firm forecast I've seen so far.

here's the big bug holding Mozilla 1.0 back; basically a collection of extremely important bugs. Also of tremendous importance, a dependency of this bug, the Party bug ... yes, we need a party for the release!

there is apparently more than one funny bug(here's the list) on Bugzilla.

Yes, somebody has taken a stab at the date. Accodring to the manifesto, we will see a few more releases (0.9.6-0.9.9) followed by 1.0 or 0.9.10 then 1.0. there will be NO other milestones. The document claims we have about half a year until the 1.0 release. This is the first firm forecast I've seen so far.

here's the big bug holding Mozilla 1.0 back; basically a collection of extremely important bugs. Also of tremendous importance, a dependency of this bug, the Party bug ... yes, we need a party for the release!

there is apparently more than one funny bug(here's the list) on Bugzilla.

Yes, somebody has taken a stab at the date. Accodring to the manifesto, we will see a few more releases (0.9.6-0.9.9) followed by 1.0 or 0.9.10 then 1.0. there will be NO other milestones. The document claims we have about half a year until the 1.0 release. This is the first firm forecast I've seen so far.

here's the big bug holding Mozilla 1.0 back; basically a collection of extremely important bugs. Also of tremendous importance, a dependency of this bug, the Party bug ... yes, we need a party for the release!

there is apparently more than one funny bug(here's the list) on Bugzilla.

Yes, somebody has taken a stab at the date. Accodring to the manifesto, we will see a few more releases (0.9.6-0.9.9) followed by 1.0 or 0.9.10 then 1.0. there will be NO other milestones. The document claims we have about half a year until the 1.0 release. This is the first firm forecast I've seen so far.

here's the big bug holding Mozilla 1.0 back; basically a collection of extremely important bugs. Also of tremendous importance, a dependency of this bug, the Party bug ... yes, we need a party for the release!

there is apparently more than one funny bug(here's the list) on Bugzilla.

Exactly. 1.0 doesn't mean finished, it means good enough to actually use. For me there's only one bug which I experience consistently enough to suggest that 1.0 should not yet be declared. I'm sure there are others that others are experiencing, though.

we need preparation as well as a good place to have the biggest & coolest party ever!

These two Slashdot-related bugs amuse me:

Bug #68974

Description:
Mozilla 0.8 cannot be released until Slashdot is ready

Bug #73658

Description:
No Slashdot story for Mozilla 0.8.1 release

It seems like there was another more recent one about not being able to release 0.9.something until Slashdot was ready and working properly, but i can't seem to find it... Maybe it was just the 0.8 one above.

we need preparation as well as a good place to have the biggest & coolest party ever!

These two Slashdot-related bugs amuse me:

Bug #68974

Description:
Mozilla 0.8 cannot be released until Slashdot is ready

Bug #73658

Description:
No Slashdot story for Mozilla 0.8.1 release

It seems like there was another more recent one about not being able to release 0.9.something until Slashdot was ready and working properly, but i can't seem to find it... Maybe it was just the 0.8 one above.

we need preparation as well as a good place to have the biggest & coolest party ever!

These two Slashdot-related bugs amuse me:

Bug #68974

Description:
Mozilla 0.8 cannot be released until Slashdot is ready

Bug #73658

Description:
No Slashdot story for Mozilla 0.8.1 release

It seems like there was another more recent one about not being able to release 0.9.something until Slashdot was ready and working properly, but i can't seem to find it... Maybe it was just the 0.8 one above.

Mozillazine is somewhat better but is something of a house organ and doesn't tend to report the negatives.

A more neutral site is Mozillanews which seems to have reasonably accurate information but not as much of it.

There is also of course the "official" Mozilla site which does have some information as well.

For more funny bug reports, check out bug 59921 - which is a tracking bug for "interesting" bug reports.

That is funny (+5) they admit that the release of 1.0 [mozilla.org] is a bug.

I think you may misunderstand Bugzilla. It's an issue-tracking system, where each issue happens to have the term "bug". So, for instance, bugs are even filed for feature requests.

Also if your have the big party and thus have this blocking bug solved i think it is not wise to release 1.0 the next day.......8-)

For the good of the code

Give to the code and the code will give to you. :P

Hey, all the team needs to do is ask.

At the bottom of the buglist we see Bug #100309

Description:
Opened: 2001-09-18 08:55

we need preparation as well as a good place to have the biggest & coolest party
ever!

that's a good bug to have

~z

I love Poland but is it really essential to fix the Polish language bugs for a 1.0 release? Aren't there more important priorities? Isn't 1.0 about a stable API (and product!) and such, and if so, couldn't fixing spelling mistakes in the Polish language pack wait until 1.0.1 or something?

The document outlines some really good principles for managing software, but this entry confuses it for me. Any Polish people here to explain why it is critical? :-)

Given the size of the dependency tree for the 1.0 milestone target it looks like 1.0 could be a little way off??

Does anybody want to take a stab at a date? Does anyboy even want to count the number of bugs on that page? ;-)

Given the size of the dependency tree for the 1.0 milestone target it looks like 1.0 could be a little way off??

Does anybody want to take a stab at a date? Does anyboy even want to count the number of bugs on that page? ;-)

I didn't see any mention of internationalization (I18N) or localization (L10N) in any part of this list. Although the Mozilla site has a section for I18N, L10N and BiDi issues, these parts of the Mozilla site seem especially quiet. The Mozilla Team has obviously been working hard on these issues; you can tell that by the features in the latest 0.9.x releases. It just seems surprising that it wasn't mentioned in the 1.0 statement. They do want World Domination, right?

I didn't see any mention of internationalization (I18N) or localization (L10N) in any part of this list. Although the Mozilla site has a section for I18N, L10N and BiDi issues, these parts of the Mozilla site seem especially quiet. The Mozilla Team has obviously been working hard on these issues; you can tell that by the features in the latest 0.9.x releases. It just seems surprising that it wasn't mentioned in the 1.0 statement. They do want World Domination, right?

I didn't see any mention of internationalization (I18N) or localization (L10N) in any part of this list. Although the Mozilla site has a section for I18N, L10N and BiDi issues, these parts of the Mozilla site seem especially quiet. The Mozilla Team has obviously been working hard on these issues; you can tell that by the features in the latest 0.9.x releases. It just seems surprising that it wasn't mentioned in the 1.0 statement. They do want World Domination, right?

Go straight to the original article instead! Mozillazine seems to be down...

However also adding:

ulimit -s 2000

worked for me. (See bug 94790)

I posted this message because I have spent ages trying to get java working on my RedHat 7.1 machine and I'm sure others have too. The LD_ASSUME_KERNEL trick doesn't always work.

But now (at last) I can dump Netscape 4.x

Ctrl+Tab and Ctrl-Shift-Tab don't work under Windows 2000/NT apparently. :(

On a positive note, gestures finally installs and works for me now. :)

First off, what it cost me in resources: I grabbed about 150Mb of source off CVS, but it was compressed. Normal Mozilla source tarballs are 35Mb so it was probably about that amount that I actually downloaded. It took a little short of half a gig (!) of disk space for the compile, and it took about three quarters of an hour to compile on a 1Ghz Duron using this configure line:
./configure --enable-xinerama --disable-debug "--enable-optimizations=-O4 -finline -fno-omit-frame-pointer -march=pentiumpro -mcpu=pentiumpro" --disable-mainnews
(most of which I snagged from some earlier /. poster, thanks!)

Secondly, what I gained over just using the normal build: Xinerama no longer makes my fonts go to comedy oversize on certain sites (reported here). But, more interestingly, Mozilla is definitely a lot snappier to use. Menus open quicker, I swear pages render faster, and it's all around more responsive.

Now to wait for a fresh Galeon to try out...

There otta be a new section to the Bugzilla software that is all about future features.

File bugs and set the severity to "enhancement".

Gerv

Here are just a few of the tools that are considered traditionally in UNIX/Linux/BSD territory that are available for Win32. In all actuality, there's enough out there to get as much of Linux running on Win32 as Win32 running under WINE.
XFree86: http://sources.redhat.com/cygwin/xfree/
KDE: http://kde-cygwin.sourceforge.net/
GTK/PHP/Libglade: http://gtk.php.net/download.php

Apache: http://www.apache.org
PHP: http://www.php.net
PHPTriad: http://www.phpgeek.com
Perl: http://www.activestate.com
Ruby: http://www.pragmaticprogrammer.com/ruby/downloads/ ruby-install.html
Python: http://www.python.org/download/download_windows.ht ml
TCL/TK: http://www.pconline.com/%7Eerc/tclwin.htm

MySQL: http://www.mysql.com
MySQL ODBC: http://www.mysql.com/downloads/api-myodbc.html
PostgreSQL: Included in cygwin (only works on NT)

ATT's U/WIN* Unix for Windows: http://www.research.att.com/sw/tools/uwin/
Cygwin: http://sourceware.cygnus.com/cygwin/
DJGPP: http://www.delorie.com/djgpp/
Native UNIX command-line binaries: http://www.wzw.tu-muenchen.de/~syring/win32/UnxUti ls.html

vi: http://www.cs.vu.nl/~tmgil/vi.html
Emacs: http://www.cs.washington.edu/homes/voelker/ntemacs .html
OpenOffice: http://www.openoffice.org

Mozilla: http://www.mozilla.org
GIMP: http://user.sgic.fi/~tml/gimp/win32/

List of GNU software for Windows: http://www.gnusoftware.com/
And so on . . .

There's a list over at DMOZ.org of a lot of this.

ftp://ftp.mozilla.org/pub/mozilla/releases/mozilla 0.9.5/

1. OpenNap
2. XFree86
3. Cygwin
4. Emacs
5. Vi and Vim
6. Mojo Nation
7. Visual Tcl
8. MikTEX
9. Open Perl IDE
10. Mozilla
11. WinCVS
12. BitchX
13. Firebird
14. mySQL

However, if you still disagree, you can always report a bug and see what everyone else says about it. Just mark it as an "enhancement" request.

Let me know when it compiles out of the box on OpenBSD

It'll do that when you, or someone else who runs OpenBSD, start submitting patches to make it do so. If you don't care, why should non-OpenBSD users care to make it run on your platform for you?

It already compiles out of the box on Linux, MacOS 9, MacOS X, Windows, OS/2, Solaris, HP-UX, OSF1, VMS, Linux/ppc, BeOS and BSD/OS (whichever BSD that is.). See here.

I'm sure more than one of those bugs will allow arbitrary file execution

Is that just FUD, or can you back it up? Why don't you say this about any other browser?

Gerv

The back button and cnn.com is bug 103978. You can vote for bug 103978.

The back button and cnn.com is bug 103978. You can vote for bug 103978.

The obvious example is one of the most frequently used. I usually suggest that people use Mozilla as their primary browser and mailer. It's still pre-1.0, but tends to be less buggy than IE, support standards better, provide more privacy features and overall saves a lot of headaches for user and admin alike.

I use the Gimp under Windows, but it's a bit clunky (especially in opening and saving files), so I would not reccomend it to everyone.

About the GPG/PGP support: This is bug 56052. Even if you cannot help, you can vote for it.

If you can't seem to get the Java plugin to work, please read the instructions in the release notes:
http://www.mozilla.org/releases/mozilla0.9.5/#java

Speaking of OmniWeb, I think a major thing going for it is that it renders its text with Quartz and looks wonderful. Recently there has been an effort to get Quartz to draw fonts in Mozilla. Check this screen shot of Quartz working in Mozilla. Cool stuff. It's only a prototype and from the bug report looks like it has a ways to go before it lands.

Speaking of OmniWeb, I think a major thing going for it is that it renders its text with Quartz and looks wonderful. Recently there has been an effort to get Quartz to draw fonts in Mozilla. Check this screen shot of Quartz working in Mozilla. Cool stuff. It's only a prototype and from the bug report looks like it has a ways to go before it lands.

There is no Java plugin for Moz/Netscape 6 yet. There has been some movement on this lately. Check out http://bugzilla.mozilla.org/show_bug.cgi?id=88870. The bug is targetted at the .96 release.

Changelog:

* The History and Mail&News applications now allow you to reorder columns with drag and drop. For instance, if you prefer to have the date listed first in your mail thread pane, drag the Date header onto the Subject header and the Date column will move to the first position.
* Warnings in the JavaScript console now show the text of the offending line.
* Venkman, the JavaScript Debugger is now available in complete installer builds. Remember to choose 'complete' install, instead of 'typical'. Start the debugger under the Tasks/Tools menu or from the command line with mozilla -venkman.
* Mozilla has a new experimental Tabbed Browsing feature. Press Ctrl+T to open a new tab. (Bug 101973.)
* People who like tabbed browsing may also like the mozilla gestures add-on, Optimoz now available at mozdev.org.
* SOCKS proxies (both v4 and v5) can now be used with all protocols (Bug 89500) except MailNews. Using socks with MailNews is covered by bug 44995.
* Mozilla has a new Site Navigation Bar for navigating sites that use the element (like Bugzilla buglists.) Choose the menu item View | Show/Hide | Site Navigation bar | Show As Only Needed to make the toolbar show up automatically when you visit pages that use the element.
* The View Source window now has a context menu with items for Find, Copy, and Select.

Changelog:

* The History and Mail&News applications now allow you to reorder columns with drag and drop. For instance, if you prefer to have the date listed first in your mail thread pane, drag the Date header onto the Subject header and the Date column will move to the first position.
* Warnings in the JavaScript console now show the text of the offending line.
* Venkman, the JavaScript Debugger is now available in complete installer builds. Remember to choose 'complete' install, instead of 'typical'. Start the debugger under the Tasks/Tools menu or from the command line with mozilla -venkman.
* Mozilla has a new experimental Tabbed Browsing feature. Press Ctrl+T to open a new tab. (Bug 101973.)
* People who like tabbed browsing may also like the mozilla gestures add-on, Optimoz now available at mozdev.org.
* SOCKS proxies (both v4 and v5) can now be used with all protocols (Bug 89500) except MailNews. Using socks with MailNews is covered by bug 44995.
* Mozilla has a new Site Navigation Bar for navigating sites that use the element (like Bugzilla buglists.) Choose the menu item View | Show/Hide | Site Navigation bar | Show As Only Needed to make the toolbar show up automatically when you visit pages that use the element.
* The View Source window now has a context menu with items for Find, Copy, and Select.

that annoying PDF plug-in that usually crashes my browser [mozilla.org].

I use xpdf with Mozilla 0.9.3. It doesn't crash, and it's not bloated at all. Also, I've had success with ggv. These are standard with many Linux distros.

__

The new open journal, JMLR that replaced the old one is a great solution to the problem. However, I'm dismayed to find that they publish using proprietary formats. Namely PDF and Postscript. Wouldn't it, thus, cost money to save to those formats? I think they should use open standards *only*. Why not use LaTex or just plain old HTML 4? This would better allow scientists from developing countries to publish their work rather than wasting precious money buying licenses of Adobe Acrobat. It seems they are fighting closed proprietary standards in the first place and should not be supporting them.

Furthermore, I could actually read the articles much easier than saving to a file and launching a bloated Adobe application or, gasp, use that annoying PDF plug-in that usually crashes my browser.

But what really sucks is that Slashcode's inane . link exposer for people who are too stupid to look at the bottom of their browser's window to see the URL that they're clicking on has basically ruined this joke.

I think the main problem is that when I have both IE and Mozilla installed, there's no easy way to have both "Open in IE" and "Open in Mozilla" in the context menu for an html file. IE and Mozilla fight for the extension, not giving you the option to have both browsers associated with the file type. If you want to change your default browser later, and you somehow manage to find the "open with..." option in explorer (shift+right-click), you have to select from a list of every application on your system rather than just a list of web browsers.

In addition to those problems, the single-program-per-extension system forces uninstallers to be unnecessarily complex. For example, if you uninstall Mozilla, apparently it's Mozilla's responsibility to tell Windows to switch back to using IE. Mozilla can't just tell Windows "I'm not here anymore, so find another program to handle html files".

And don't even get me started on how hard it is for a browser to determine whether it's safe to open an untrusted file with its default application. Apparently the solution is to hard-code a long list of "dangerous" extensions from Microsoft's web site into your browser. At least Microsoft isn't trying very hard to establish a monopoly on secure web browsers...

I think the main problem is that when I have both IE and Mozilla installed, there's no easy way to have both "Open in IE" and "Open in Mozilla" in the context menu for an html file. IE and Mozilla fight for the extension, not giving you the option to have both browsers associated with the file type. If you want to change your default browser later, and you somehow manage to find the "open with..." option in explorer (shift+right-click), you have to select from a list of every application on your system rather than just a list of web browsers.

In addition to those problems, the single-program-per-extension system forces uninstallers to be unnecessarily complex. For example, if you uninstall Mozilla, apparently it's Mozilla's responsibility to tell Windows to switch back to using IE. Mozilla can't just tell Windows "I'm not here anymore, so find another program to handle html files".

And don't even get me started on how hard it is for a browser to determine whether it's safe to open an untrusted file with its default application. Apparently the solution is to hard-code a long list of "dangerous" extensions from Microsoft's web site into your browser. At least Microsoft isn't trying very hard to establish a monopoly on secure web browsers...

Yes, folks, this guy is in charge of quality for Mozilla, but he doesn't have the sense to test his own URLs. That should tell you something right there. So should the bug chart.

The Patch Maker story ran in mozillaZine on Sept 27 -- quite a long time ago and there was quite a lot of discussion there, why couldn't slashdot have posted that link then?

I suggest if you want to follow Mozilla news, go to mozillaZine and along the right-hand navigation click on the "Add Sidebar Panel" item (I'd make a link here but it needs more than a URL to make it go). Or go to one of the newsgroups, or watch the top items on Bugzilla (a great source for what's on the developer's mind). There's also This RDF newsfeed for top newsgroup threads. Am I making my point? Don't waste your time at mozillaquest, go to the real deal.

Take a look at the docs at Mozilla's site:

http://www.mozilla.org/hacking/patch-maker/

I have to say that with the Tab interface, support for the LINKS toolbar, and all of the other cool things Moz has been picking up lately, it is really becoming a brilliant application. I cringe when I am stuck using I.E. now.

Darn, Slashdot doesn't like title attributes in links :( Repost with good links

So the Mozilla developers are hoping to get more bug-fixing help from the Mozilla and Open Source communities by making it easier for people to write and submit bug-fix patches.

He actually got something right! It's not just developers hoping to get more bug-fixing help though. The Mozilla QA and testing community can use help as well. Gerv (creator of the Patch Maker) is also the maintainer of the Bugzilla Helper which, like the patch maker, was created to make it easier for people to contribute to the Mozilla project. If you're interested in helping to make Mozilla better and you've got DTML skills then you can probably help clean up the Mozilla UI with Gerv's Patch Maker. If you're interested in helping but aren't interested in development there are plenty of other ways to get involved.

--Asa