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

From: Neil MacLeod gmane at nmacleod.com
Date: Thu Aug 2 16:37:30 EEST 2007
Eero Tamminen wrote:
> Hi,
> We certainly know what we've fixed, but the issue is that there's
> no reasonable way to know what part of that is relevant to you.

At the very least publish those bugs that are aliased to bugs in the Public bugzilla. You have the public bugs aliased to internal bug references and I assume (bad I know) that a similar relationship exists internally in which case simply pull out those aliased bugs that are fixed in the most recent release. Any half-decent bug tracking system should allow this type of query.

> I don't think anyone here is willing to take the cost of e.g. testing
> all the major bugs fixed from the intermediate development releases and
> test whether they can be also replicated in the previous public release,
> especially as <1% of that work would actually produce anything to the
> release notes (and even less to end-user release notes) and this large
> testing cost (for example some tests need quite elaborate setups)
> wouldn't do anything to make the new release any better!

Is there any scope here to introduce automated testing? It sounds like that's what you need.

However I fail to understand what your point has to do with the generation of a changelog.

> 	- Eero

More information about the maemo-developers mailing list