[maemo-developers] Backwards compatibility broken PR1.1 SDK
From: Graham Cobb g+770 at cobb.uk.netDate: Tue Jan 19 13:04:17 EET 2010
- Previous message: Backwards compatibility broken PR1.1 SDK
- Next message: Backwards compatibility broken PR1.1 SDK
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tuesday 19 January 2010 08:17:25 David Greaves wrote: > Graham Cobb wrote: > > I do think there may be an option 1.5: create multiple autobuilder queues > > which feed the same repository but build against different SDK releases. ... > > I like - but as someone mentioned to me in a similar situation: testing. > > We'd need testers for each queue and that may be tricky. Do we? I have a goal that all applications install on as many releases as possible and only use a restricted version queue if they **really** have to. I don't want to create processes that give developers incentives to use a restricted queue -- quite the opposite. The tradeoff is that that means that many applications will not be able to have been tested against all the possible releases they might see. But this is very little different from an application being out there when a new release happens. Otherwise we will find that many applications are just not available to most of our users. I predict that by the time Maemo 6 ships, half of all N900's sold will still be running the release that shipped from the factory. Anyone got any data? Graham
- Previous message: Backwards compatibility broken PR1.1 SDK
- Next message: Backwards compatibility broken PR1.1 SDK
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]