Translation refresh

[Bernie Innocenti]

Kim Quirk wrote:

> Collaboration is really important to any release... so we need to include
> some activities that collaborate as part of formal testing. Similarly,
> Journal is much more than just an activity... so that will have to be part
> of systematic testing.
> 
> Browse has to work as it is our connection to the outside world and to our
> local or school library. So that will have be part of any good test plan.

What version(s) of Browse and other important activities are we going
to test each OS release with?

Here's an example: I installed the G1G1 activity pack "some time ago",
and I don't even know what versions of activities I'm using.

Will this random bunch of activities keep working when Update.2
comes out?   Vice-versa, can we expect activities released next
year to work with my build 703 system or will I be forced to
upgrade at some point?

The complexity of an N-to-M compatibility testing is the reason
why Linux distributors tend to bundle all the existing
applications with the OS (either on installation media or on
online repositories).

Not addressing these dependencies now will lead to the same
compatibility hell that has swamped a well known desktop OS.

-- 
   \___/
   |___|    Bernie Innocenti - http://www.codewiz.org/
    \___\   CTO OLPC Europe  - http://www.laptop.org/