Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
Note: You can take 10% off all Slashdot Deals with coupon code "slashdot10off." ×

Comment Non-Issue (Score 1) 386

This is completely a non-issue, the majority of people are on the main builds and you can specify in your program what firmware and hardware it requires so that it doesn't show up for people that can't run it. I'm not too worried about developing for the 3 people running Bub's AOSP Magic "Original" v 0.3.3. Fragmentation is a boogie-man and nothing more.

Comment One size turnaround time doesn't fit all (Score 1) 418

It really depends on the system, the problem and the people involved. The system we run where I work has changes put into it in production daily with turnaround times anywhere from an hour to several weeks depending on the change. We have some customers where a fix can be worked on and implemented over the course of weeks due to testing and they have no problem with that and we have customers that expect things to be fixed later today. The real question to ask yourself and your team is is it reasonable in your product or system to be able to turnaround something that fast?

"Falling in love makes smoking pot all day look like the ultimate in restraint." -- Dave Sim, author of Cerebrus.

Working...