Mozilla 1.1alpha Coming Soon
Monday June 10th, 2002
In a posting to netscape.public.mozilla.seamonkey, Asa Dotzler says, "We've taken somewhere in the neighborhood of 1700 fixes on the Mozilla development trunk since 1.0 was branched about two months ago. These fixes include a few new features and other 'heavy lifting'. If all goes well with testing, the 2002-06-10 evening builds or the 2002-06-11 early morning builds will be released as 1.1 Alpha in the next day or two.
"1.1a is not a Mozilla 1.0 bugfix follow-up. That will be called 1.0.1 and will contain the limited and more conservative work currently underway with the 1.0 branch. See <http://www.mozilla.org/roadmap.html#tree-management> for a picture of what this looks like.
"This 1.1a release is from the less conservative (and probably less stable) Mozilla development trunk and is intended as a checkpoint for gathering feedback and crash data. So if you use these Alpha builds be warned that they are unlikely to be as stable as Mozilla 1.0 or the upcoming 1.0.x releases. But the 1.1a releases will have new features and big improvements to performance so give them a try and don't forget to send in any TalkBack reports."
It's about time talkback was actually made to work properly with proxy servers, I use the squid proxy (with username/password authentication) - I haven't been able to get talkback to work with this - I can configure the hostname and port of the proxy server but not the username and password - anyone else have any luck with this?
Hey, my subject is the same as my last post, instead of Re: ___ whatever.
I've used the Proxomitron <http://proxomitron.org/> to send the username and password to an authenticating proxy server on Windows.
#18 Re: Re: Talkback Proxy Problems..
Monday January 22nd, 2007 8:45 AM
The URL above is no longer valid. You can read <<http://kb.mozillazine.org…nt#No_incident_IDs_listed>> for more details about using The Proxomitron to get the Quality Feedback Agent (QFA) to work with proxy authentication.
#2 Time and priority distribution?
Tuesday June 11th, 2002 5:02 AM
I wonder what the relative priorities for trunk and branch work are for the mozilla staff people, especially those who are needed by contributors (drivers, module owners how do r, sr, user interface experts etc.). Is there a strategy how manpower should/will be distributed between the two?
#8 Re: Time and priority distribution?
Tuesday June 11th, 2002 10:21 AM
My understanding is that the development will take place on the trunk and if a fix is important enough, it'll get migrated to the 1.0 branch. I imagine the distribution would be somewhat as it has been since 1.0 branched, but with more emphasis on the trunk.
When next release is 1.1a, will bugs targeted 1.1a be priority 1? And then bugs targeted 1.0.1? And bugs targeted 1.0, will they be moved to 1.0.1/1.1a?
I've been using 1.1alpha, the June 7 build, for several days now. There are very few problems. Submission of forms is a bit slow, and there are a few other issues. Necko seems to stop occasionally. Overall, it feels more complete than 1.0. There's download manager, which is actually pretty nice now that I'm used it. We've also got the Site Navigation Bar (for link tags). Hopefully we can get that converted to XBL so it will make the 1.1 branch. See <<http://bugzilla.mozilla.org/show_bug.cgi?id=102992>>. BTW, Bugzilla is really slow this morning. Wasn't there an upgrade last night?
Uh, make that <a href="<http://bugzilla.mozilla.org/show_bug.cgi?id=102992>">this bug</a>.
Gotta love it. Let's try it this way:
> Necko seems to stop occasionally.
this is very alarming... can you provide some more information about the failure. do you have pipelining enabled? is the problem reproducible? is there a bug filed? thx in advance!!
I just mean that it seems to pause sometimes. What I think I'm actually seeing, though, is that the rest of the app pauses while Necko is trying to download things. This shows up particularly while switching windows. If one window is slowly downloading a page, and I switch to a new window, the second window might not come to focus until the first window begins to display. I see this with HTTP/1.1, both with and without pipelining. Is that Necko?
#11 Mozilla 1.1a puts the A in Alpha
by _rgw_ <email@example.com>
Tuesday June 11th, 2002 11:34 AM
Ok, that was corny, but 1.1 will certainly have an alpha-ish feel to it. That is to be expected because of the large amount of patches added and having less testing then then the 1.0 branch. 1.1a should perfrom to bad for an alpha.
#12 a question-
by alossiX <alossiX@yahoo.com>
Tuesday June 11th, 2002 2:40 PM
are patches made to the 1.0.x branch also added to the trunk?
no. patches are made to the trunk and then sometimes also added to the branch. the trunk takes all fixes and the branch takes a subset of all fixes deemed safe enough for the stable branch.
Is there a roadmap for the new stuff?
#15 Re: What new features?
Tuesday June 11th, 2002 3:27 PM
yes. see the link in the topic <http://www.mozilla.org/ro…dmap.html#tree-management>