[maemo-developers] 3.2007.10-7 - Detailed change log?

From: Neil MacLeod gmane at nmacleod.com
Date: Fri Aug 3 20:19:40 EEST 2007
Eero Tamminen wrote:
> It's not so much "withholding" the information as getting
> somebody spending large effort on collecting, filtering/reducing
> and translating this information to publicly relevant/usable form.
"Someone" only has to spend a large effort on collecting, filtering etc. *IF* you don't have a process in place to flag bugs for disclosure as bugs are entered into your internal bug tracking system. If bugs are flagged appropriately as they are raised then creating a changelog becomes a no brainer. Hell, you could automate it and publish a daily changelog.

But if you don't have a process, you end up devoting vast amounts of effort to clear up the mess caused by the lack of any such process.

If you were to implement such a process today, by the time of the next release a large number of bugs might be suitable for automatic disclosure. Pre-existing bugs would need manual flagging which could be performed as bugs are closed etc.

> As an open source developer I hope that eventually as the platform
> becomes more open, the significance of proprietary part fades away
> (because there's so much cool stuff on the open :)).  As the community
> starts to participate more in the Maemo development, I see the
> importance (and benefit) of concise whole distribution changelog
> increasing.  But when the platform opens more, the people from the
> community could also provide it...  Nokia changelog would anyway
> be boring "consumer" related thing lacking all the cool technical
> details, I feel maemo-developers want something more snazzy. ;-)
I have a bad feeling that by the time Nokia have opened their platform sufficiently to allow full community involvement, there won't be any community left - we'll have moved on to other projects that don't require us to debate the production of the most fundamental items of information pertaining to each release.

Let's face it, the existence of two bug tracking systems (one internal and one public) isn't helping matters nor is the repeated promises that the situation will improve when there is little evidence of this happening - there is precious little Nokia involvement in the public Bugzilla, bug #1204 being a prime example. Why is it not possible to use the public bugzilla to track the majority of the bugs? I'm sure your internal system is tracking bugs that we also eventually find, but why do we have to double up on bug detection and reporting duties?

Changelogs though are fundamental, and I don't really care for Nokia bureaucracy or inefficiency. I realise that's not your fault, and I'm sorry to say that it's this Nokia bureaucracy that is going to kill the Nokia Internet Tablet project as developers move on to other projects where they don't have to bang their heads against these kind of brick walls.

More information about the maemo-developers mailing list