Talk:Software Release Notes
How old is this article?
Is there a reason new users need to wade through pages like this after searching wiki.laptop.org? And what does Ship.2 or whatever refer to? I know a bit of build 650, 653, 656 or numbers like that, never ship_2.... Somebody needs to take ownership of obsolete pages and put them somewhere somehow so when one is searching for help, they get more current info first. The articles need to state if they are build version specific, or attempt to cover <subject> for a set of build versions. The former articles can be obsoleted or depreceated? after some point, the latter need to be continually maintained. If this comment is out of line I have no problem is somebody who knows better removes it. 76.115.84.114 15:52, 19 June 2008 (EDT)76.115.84.114 15:56, 19 June 2008 (EDT)
- If you follow the link at the top of the page (the one saying "NOTE: This page is about to be replaced by OLPC_Ship.2_Software_Release_Notes. "), you will go to the Ship.2 notes and see that Ship.2 = build 703. There is no problem with pointing out things that are confusing to new users, of course, the "wiki" response is to make some edits to improve it. That said, there is no doubt that the terminology can be a little confusing at times, but it is what it is. This is not just a user-help-manual site, it is a peek inside an ongoing technology project as-it-happens. It was known that there would be a "Ship.2" (the second major build shipped on factory-built machines) long before it could be known which number that was going to be. Ship.2 was basically a placeholder name for whichever build-number was going to meet the criteria set for the things that were needed/wanted in the second major build on shipping laptops. As for how old any given article may be, just check the edit history and see for yourself. Cjl 17:59, 19 June 2008 (EDT)
"known performance problems"
"Most of our effort to date has been consumed by basic device support as well as putting together the basic user interface framework for children, which has known performance problems."
This was to be expected, no? It's in Python. People use C if they care about performance. (with bits of assembly if they REALLY care)
(or FORTRAN maybe)