Too late now, girls!
I'm sure every girl on his school/university had the chance to go out with him.
But you refused. You decided to go out with Football players and the like. Now who's the billionaire?!?!
Next time, think twice when you're thinking with whom to go out...
All this guy did was copy & paste someone else's work for his own benefit.
But you're still new here, my young hotshot... Everything must seem frightening and confusing to you... Have no fear, 830897, there's still much to learn...
I promised I'd get to all of your questions from my making releases happen post and I've finally got a few minutes free to take a stab at it.
Some of the questions overlap and some would take a lot more time to answer than I've got for this post but I've done my best to put together replies to each of the questions. I'm put my responses together in the format of direct replies to each of the people who had questions. Maybe later I can distill this into a more condensed post about the release processes at Mozilla.
This took a good bit longer than I expected:-) (hours, not minutes) so I haven't done any serious proof reading; please excuse grammar or spelling issues. Also, this is just one man's opinion and if I've got something wrong here or misrepresented anything, pin that on me and not on drivers@mozilla.org or other members of the community.
Peter van der Woulde was the first to post questions, so he gets the first set of answers.
1. How do you decide what to plus and what to minus ?
This is probably one of the most frequently asked questions and our process isn't based on a set in stone list of rules. As I'm sure you know, there are two types of flags we evaluate and set. The first is the "blocking" bug flag and the second is the "approval" patch flag. The blocking flag is for bugs which should stop the shipping of that particular release and the approval flag is for patches which should land during the freeze for that release.
It's probably also important to realize that there are about a dozen of us on drivers@mozilla.org and we all come with different expertise. I am particularly focused on quality and how our testing and user communities will respond to each of the product releases. Others have a focus on things like Web standards, security, freezing and maintaining APIs, or the Mozilla application platform. We all approach the plussing and minusing of bugs and patches with a somewhat different set of criteria.
There are a lot of factors that come in to play, but I think over the years all of drivers have come to settle on some basic tenants.
First, our criteria for alpha, beta, and final cycle changes are all different. We're going to have a different approach to determining whether or not a bug should block an alpha release than we would for a final release. We're also going to be a bit more relaxed about the kinds of patches we approve to land during an alpha freeze than we would for a final release freeze.
Alpha cycles can absorb more risk than beta and final cycles so we're likely to try to use drivers@mozilla.org's influence to get high risk patches (including features, major code rewrites or reorganizations) landed in the alpha cycles. I'd certainly rather hold an alpha release for a day or two in order to get the added testing on a major new feature before beta and I'd be willing to approve the landing of that change during the alpha freeze when I might push out lower-impact changes to the beta. It is sometimes a bit odd that we approve higher risk changes and deny lower risk changes, but there's some sanity behind it:-)
In a beta cycle, we are working to get our features in and all of our localizable resources frozen so we chase down any last feature changes, especially those with localizable strings. Our blocking and approval flag setting during beta are heavily influenced by our desire to get those changes all settled so that our testing and localization communities have a clear idea of what we plan to ship by final and we can get good testing coverage and as many complete localizations as possible.
During the final cycle, usually on the branch, we're all about minimizing risk and preventing changes that would break localizations. In addition to those criteria, we are looking for spit and polish changes, stability improvements (any low-risk topcrash fixes) and those routine chan
In the NYTimes.com picture, they added a leaf... Is this some American thing?/European
Of course The American Version Is The Correct Version. Don't trust Our Media? The danish version is just a filthy porn version from this well-known immoral little country.
You don't understand. You DON'T want your grandmother to install stuff on her PC.
I know. BUT sometimes she brings a CD with a encyclopedia, or whatever. And she wants to install it. And she does. And next time I visit her I find out she has installed 3-4 new programs and there was no need to call me.
why not just go for the el cheapo special from dell or someone and then install Linux on it?
I tell you why the Mac Mini is better suited for your grandmother:
iMovie
iPhoto
overall better quality
easy-to-install software (my grandmother CAN install software on her iMac, yet I don't think she could do on a Linux-box)
No offense meant against Linux, it's a great OS (while I prefer BSD, which is dying, and MacOS). Yet I think Mac OS and Macs in general are more granny-compatible
I know I'm feeding a troll... but, you know, there are much cheaper offers than £60. In fact, I've never seen this game at SUCH a high price, even when it was all new...
Not true. I work in a advertising agency and we use JPEG quite often. We still use a lot of TIFF and EPS and whatever (I'm a texter, so I don't know too much). But when I show a JPEG picture to the art director he asks "what resolution?" and "let me see it" to determine if he can be use it.
If you leave the slider on the "high-quality"-side when you compress a picture it's virtually identical to the uncompressed one, but much, much smaller.
1 MB of RAM? Even with 128K RAM the first Macintosh was reeeeally expensive. Maybe today you think that 1 MB RAM "couldn't have been so expensive in 1984". Believe me: it was expensive (but I'm too lazy to look it up) Hey, at least the Mac was capable of adressing more than 640K (though that "should be anough for everybody")
this list included much of what one might expect as common subjects of photos: cat, friends, dog sky, sea, park, kids, garden, baby, building, flower, flowers signs, sculpture, city, vacation.
"There are a lot of similarities with the drug war,"
Or when will these geniuses realize that the same is true about the war on terror? Of course there are even more lives and money wasted on fighting it...
Slashdot Mirror
That's exactly what I'm going to do now.
Unfortunately, my girlfriend hates this game...
Too late now, girls!
I'm sure every girl on his school/university had the chance to go out with him.
But you refused. You decided to go out with Football players and the like.
Now who's the billionaire?!?!
Next time, think twice when you're thinking with whom to go out...
What happens if Slashdot puts a link to mirrordot? Will mirrordot mirror itself?
Then, my friend, the internet will hang up, which will ultimately lead to the destruction of the universe.
we need a
How about
You're misunderestimating the author.
All this guy did was copy & paste someone else's work for his own benefit.
But you're still new here, my young hotshot...
Everything must seem frightening and confusing to you...
Have no fear, 830897, there's still much to learn...
Copy&paste:Here's TFA (the answers):
:-) (hours, not minutes) so I haven't done any serious proof reading; please excuse grammar or spelling issues. Also, this is just one man's opinion and if I've got something wrong here or misrepresented anything, pin that on me and not on drivers@mozilla.org or other members of the community.
:-)
I promised I'd get to all of your questions from my making releases happen post and I've finally got a few minutes free to take a stab at it.
Some of the questions overlap and some would take a lot more time to answer than I've got for this post but I've done my best to put together replies to each of the questions. I'm put my responses together in the format of direct replies to each of the people who had questions. Maybe later I can distill this into a more condensed post about the release processes at Mozilla.
This took a good bit longer than I expected
Peter van der Woulde was the first to post questions, so he gets the first set of answers.
1. How do you decide what to plus and what to minus ?
This is probably one of the most frequently asked questions and our process isn't based on a set in stone list of rules. As I'm sure you know, there are two types of flags we evaluate and set. The first is the "blocking" bug flag and the second is the "approval" patch flag. The blocking flag is for bugs which should stop the shipping of that particular release and the approval flag is for patches which should land during the freeze for that release.
It's probably also important to realize that there are about a dozen of us on drivers@mozilla.org and we all come with different expertise. I am particularly focused on quality and how our testing and user communities will respond to each of the product releases. Others have a focus on things like Web standards, security, freezing and maintaining APIs, or the Mozilla application platform. We all approach the plussing and minusing of bugs and patches with a somewhat different set of criteria.
There are a lot of factors that come in to play, but I think over the years all of drivers have come to settle on some basic tenants.
First, our criteria for alpha, beta, and final cycle changes are all different. We're going to have a different approach to determining whether or not a bug should block an alpha release than we would for a final release. We're also going to be a bit more relaxed about the kinds of patches we approve to land during an alpha freeze than we would for a final release freeze.
Alpha cycles can absorb more risk than beta and final cycles so we're likely to try to use drivers@mozilla.org's influence to get high risk patches (including features, major code rewrites or reorganizations) landed in the alpha cycles. I'd certainly rather hold an alpha release for a day or two in order to get the added testing on a major new feature before beta and I'd be willing to approve the landing of that change during the alpha freeze when I might push out lower-impact changes to the beta. It is sometimes a bit odd that we approve higher risk changes and deny lower risk changes, but there's some sanity behind it
In a beta cycle, we are working to get our features in and all of our localizable resources frozen so we chase down any last feature changes, especially those with localizable strings. Our blocking and approval flag setting during beta are heavily influenced by our desire to get those changes all settled so that our testing and localization communities have a clear idea of what we plan to ship by final and we can get good testing coverage and as many complete localizations as possible.
During the final cycle, usually on the branch, we're all about minimizing risk and preventing changes that would break localizations. In addition to those criteria, we are looking for spit and polish changes, stability improvements (any low-risk topcrash fixes) and those routine chan
What true American would call Denmark "well-known"?
Is that you, George? Remember, Denmark is Brigitte-Nielsen-country.
In the NYTimes.com picture, they added a leaf... Is this some American thing?
Of course The American Version Is The Correct Version. Don't trust Our Media?
The danish version is just a filthy porn version from this well-known immoral little country.
Book your next holiday on Mars with our patented one click shopping!
Good morning!
Wasn't this thing announced on Tuesday?
You don't understand. You DON'T want your grandmother to install stuff on her PC.
I know. BUT sometimes she brings a CD with a encyclopedia, or whatever.
And she wants to install it. And she does.
And next time I visit her I find out she has installed 3-4 new programs and there was no need to call me.
why not just go for the el cheapo special from dell or someone and then install Linux on it?
I tell you why the Mac Mini is better suited for your grandmother:
No offense meant against Linux, it's a great OS (while I prefer BSD, which is dying, and MacOS).
Yet I think Mac OS and Macs in general are more granny-compatible
I know I'm feeding a troll... but, you know, there are much cheaper offers than £60.
In fact, I've never seen this game at SUCH a high price, even when it was all new...
Should robots be like us?
What like depressed and self destructive?
Marvin, is that you?
True professionals don't use JPEG
Not true. I work in a advertising agency and we use JPEG quite often. We still use a lot of TIFF and EPS and whatever (I'm a texter, so I don't know too much). But when I show a JPEG picture to the art director he asks "what resolution?" and "let me see it" to determine if he can be use it.
If you leave the slider on the "high-quality"-side when you compress a picture it's virtually identical to the uncompressed one, but much, much smaller.
What's an iceburg?
From German:
Berg (as in iceberg): mountain
Burg (as in, umm, iceburg): castle
So I guess this iceburg is some mad scientist's hideout (Dr. Frost or whatever).
I wonder what it's using the rest of the week... Maybe it goes into passive mode (or does this only happen on Sundays?
In 1984, 1 MB of RAM cost about 350$.
And that was when you could buy a house for 500$. Ah, well, not quite. But the price is correct (more or less).
Well even if it was up to $50 dollars a meg or even $100 dollars then it would have been worth it for speed all applications, can then use!
This was the price in the late 80s, if I remember correctly. At that time, I was proud owner of a 386SX with 1 MB RAM.
This could then be implemented in about 1MB ram
1 MB of RAM? Even with 128K RAM the first Macintosh was reeeeally expensive. Maybe today you think that 1 MB RAM "couldn't have been so expensive in 1984". Believe me: it was expensive (but I'm too lazy to look it up)
Hey, at least the Mac was capable of adressing more than 640K (though that "should be anough for everybody")
this list included much of what one might expect as common subjects of photos: cat, friends, dog sky, sea, park, kids, garden, baby, building, flower, flowers signs, sculpture, city, vacation.
From the folksonomy thing. What's a "dog sky"?
"There are a lot of similarities with the drug war,"
Or when will these geniuses realize that the same is true about the war on terror? Of course there are even more lives and money wasted on fighting it...
I'm building a house and hoping to be out on the bleeding edge of home automation. There is some very cool IP-based stuff coming out.
When we get your IP number, you'll be slashdotted.
All your house are belong to us.
will it talk to exchange?
that's the only reason people i know use outlook...
There is one more... It comes with MS Office, which they have anyway.