[maemo-developers] Keeping Glib up to date (was RE: Diablo, do we need a separate repository?)

[From: Quim Gil]

ext Graham Cobb wrote:
> Nokia 
> should be keeping all system libraries up to date and should be scheduling 
> testing, to verify that the updated libraries do not break anything, as part 
> of the release cycle.  It is part of Nokia's responsibilities to its 
> development community.

Sure, and using fresh libraries is the general intend. For the
development community and the own Nokia developer teams.

Then real life comes with just one predictable thing: every day has 24h.
And one clear goal: we need to ship the next release on week nn.
Architect decisions are made, some go through, some go back, some go
through again after some work... But not even glib will put in risk a
deadline if it's not worth from a consumer point of view. Other software
projects might have different priorities and that's fine.


> During the life of an installed release, I agree.  Between Nokia-issued 
> firmware releases, I disagree.  My view (I realise you disagree) is that at 
> each new release Nokia should update all shared libraries.

We don't work release after release. There is ongoing plans and
development at different stages on different releases. Even if football
fans and media present each game as 90 minutes where a team has to put
all the flesh, in the coach's mind there is a couple of national
competitions, the European competition, the players that will go to the
national team on specific dates... You need to make some sense of all
that without burning your team.

Same for us developing software, more or less. Chinook was a major
release (4.0), Diablo is going to be a minor release from a platform
point of view (4.1) and Diablo+1... we will start talking about it soon.

-- 
Quim Gil
marketing manager, open source
maemo software @ Nokia