Minutes of the mozilla.org Staff Meeting of Monday 19th April 2004
Tuesday April 27th, 2004
The minutes of the mozilla.org staff meeting of Monday 19th April 2004 are now online. Issues discussed include Mozilla 1.7 final, Mozilla Firefox 0.9, Mozilla Thunderbird 0.6 and developer.mozilla.org.
URL spoofing with username:password bug <http://bugzilla.mozilla.org/show_bug.cgi?id=232567> -- Looks like for 1.7, URLs with the form <http://www.mozilla.com>:<firstname.lastname@example.org> will throw up a popup dialog box every time you go to a site using this method. Eventually, the intent is to make it warn, and the warning could be disabled on a per-site basis. Until then, a pref to disable the feature will have to do.
It looks like the FTP upload UI is working? Yay! <http://bugzilla.mozilla.org/show_bug.cgi?id=24867> -- But will it be in 1.7 final?
From the article...
"We need to land a few biggish changes we want to take on the 1.7 branch first [...] FTP upload"
I'm boycotting because nobody liked my mockup :(
#4 Tho this may be case of if u dunno, shouldn't care
Wednesday April 28th, 2004 4:42 PM
What's DevMo? Thanks.
#5 Re: Tho this may be case of if u dunno, shouldn't
Wednesday April 28th, 2004 5:37 PM
As far as I can tell, DevMo is an effort to create a central, Mozilla Foundation sponsored developers' website. They want to have something along the lines of Microsoft's MSDN web site but for Mozilla developers, extension and theme developers, etc...
Should be quite a good deal once it's online.
#7 Too soon for stable version?
Thursday April 29th, 2004 11:14 AM
Does anyone else get the impression that 1.7 is too early for the next long-term-stable release and that it would be better to * defer all new development work to 1.9 * make 1.8 a "clean-up and stabilize release" with a due date of about 3 months (2004-08) * have 1.8 be the next long-term release rather than 1.7
My gut feeling is that you're right. However if they take long enough (e.g. a couple of months) then they might acheive the goal of a stable release, and have it out in the right time-frame. Stabailising 1.8 might push the release date further, or not. I don't know if stabalising a branch will mean they have fewer resources focusing on it than if they made 1.8 the long-term stable candidate. 1.8 seems like a nicer number than 1.7 too ;)