Quote from mateli on August 25, 2011, 09:22
Quote from liz on August 24, 2011, 22:20
We'll put it on the list of things to think about. (Have to say, at the moment, that's a lengthy list…)
Remember to save some for the next generation of the device
To many projects turn into vaporvare because they never release anything. There are functionality enough on the board for many of us, so lets launch it asap. Then let the hardware developers move on to the next generation (2012) while the rest of us (software developers and users) is developing cool applications for the boards being produced...
Remember that the target is to make a cheep device for schools, a target that suffers if the device is delayed because it is overdesigned.
Lets push everything that is not a hard requirement for 1.0 to the next generation. Test the alpha, fix all blockers - then release. And then start adding more stuff and repeat the development cycle. Look at the success of the fixed ubuntu and fedora schedules for this. 6 months releases may be hard for a hardware project but 12 months should be fine.
Don't worry, most of this stuff will be for a future device. We still need your suggestions though in case something really obviously missed turns up.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed.
I've been saying "Mucho" to my Spanish friend a lot more lately. It means a lot to him.