We need a roadmap for 0.9, and to kick it off I want to set some short-term goals we can accomplish before we get too lost in the heavy weeds of architecture.
Furthermore, there is a bunch of stuff that is going to be happening sooner rather than later, just wanted to give a heads up on what it is
I'm sitting here in my "sunny" San Francisco hotel overlooking the new Apple store on 4th and Market, thinking about heading to the main prep room to don my reality distortion suit. It's made of 5" thick space-age material which, if it does its job, will protect me from the standing waves of reality distortion projected from the stage and repeated by the large towers around the conference hall. Any rip or tear, even of the smallest magnitude, will allow these waves to enter the suit, and thus my defenseless mind, filling me with euphoria and thoughts that FruitCo won the OS wars and has 95% marketshare.
But, try as I might, I know the suit won't be enough to protect me. I am a Fruit Warrior.
Russia has gained notoriety for its large number of talented and often disaffected young computer experts, whose bedrooms are regularly suspected of spawning major viruses.
How sweet it is. Where's the champagne? Camino 0.8 is live, visit mozilla.org to see it's prominant status on their homepage and download it.
I know what feedback we'll see (the "distasteful new icons" and how we "ruined it by removing the bookmarks drawer"...yes, both real comments), but it's all worth it.
I want to thank everyone involved in the project (coding and QA), as well as the Mozilla Foundation. Now, finally, on to Camino 0.9!
From some rough numbers (version tracker + 3/4 of the Mozilla FTP mirrors), we've received 50,000+ downloads of Camino 0.8b since we released it a month ago.
That's not too bad for a beta of a project that nobody gets paid to work on.
I landed a slew of stuff tonight. If you go looking, you'll see that the 0.8 buglist is at three (3) bugs. Remember when we were at 60? Tomorrow's build (2004061708-0.8b+) will be the first final candidate build for release, Camino 0.8 FC1. Download it and bang the heck out of it. At this point, only serious regressions introduced within the last week or two and bugs that eat your computer or cause the death of someone's grandmother will cause a respin. We'll probably go about a week and then release.
I'll put up a url after tomorrow's nightly goes up.
The 800-lb gorilla of sports television, ESPN's SportsCenter, is now showing in HD several times a day on ESPN-HD. Using their new HD production studio, ESPN intermixes live HD anchors with 4x3 SD highlights (and sometimes HD highlights when available). It looks pretty good, believe it or not.
The most notable impact to regular ESPN-HD viewing is that now even their non-HD programming is 4x3 with side-bars rather than the poorly stretched abomination they used before. I can actually watch ESPN-HD now, even for regular SD content. Interestingly, the sidebars aren't fixed graphics, but move ever so slightly to prevent burn-in (for those who haven't correctly calibrated their monitors). A nice touch.
So now that even the gorilla is in HD, what will this do to the already steadily rising HD viewership? Given that it's generally men driving the purchase of HD sets and set top boxes, the fact that a show highly watched by Joe Six Pack is now HD bodes extremely well for continuing that trend. We've turned a corner, there's no going back. What's next? For starers, cable and satellite companies fully carrying HD locals. Getting rid of the UHF antennas that have found their way back onto our roofs and living rooms is one more step on the evolutionary ladder. As long as Joe Six Pack needs a separate antenna for local HD programming, his hands are tied.
You asked for it, you got it. I finally fixed bug 163274, session history menus on the back and forward buttons. Should be available in tomorrow's nightly on both the trunk and branch.
Enjoy. I'm off to Gettysburg for the weekend.
I spent tonight triaging the 0.8final buglist down to about 10 (including landing some outstanding patches). My goal is
On another note, I changed the prev/next tab key shortcuts to Command-Option-Left/Right Arrow. I'm sure this will start a brand new debate on why it's a terrible choice but fixes a bunch of localization bugs.