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

From: Andrew Flegg andrew at bleb.org
Date: Fri Aug 3 19:41:49 EEST 2007
On 8/3/07, Guillem Jover <guillem.jover at nokia.com> wrote:
> On Fri, 2007-08-03 at 16:39:07 +0100, ext Andrew Flegg wrote:
> > On 8/3/07, Eero Tamminen <eero.tamminen at nokia.com> wrote:
> > > Please check what's available; kernel and X git repositories you
> > > should find with Google, [...]
>
> > OK, so the only changelog we need is:
> >
> >   * Moved from vX.Y.Z to vX.Y.Z2 of Xorg
> >   * Moved from v2.6.20-arm-rmk0 to v2.26.23-arm-rmk1 of Linux kernel
> >   [...]
>
> Err, then I think the problem is that people don't seem to be talking
> about the same things here.
>
> When I read people demanding changelogs, for me that maps to
> debian/changelog or GNU style kind of ChangeLog in the source tree.
> Any package w/o a proper descriptive changelog is broken IMO, and it
> must be fixed.

Agreed, but Eero's contention was that that information is entirely
available upstream. If we've got the detailed release notes for what
versions of upstream components are in a particular release, the
detailed changelog can be derived - IF there are no locally applied
patches.

> > Of course, this presupposes there are absolute *zero* patches that
> > you're maintaining internally for these things which aren't upstream.
>
> I say that presupposition is wrong. Take Debian as an example, most
> of the packages contain changes relative to upstream, yet this is not
> announced in any kind of distro-wide Release Notes. It's present,
> though, on the particular NEWS.Debian files or debian/changelogs.

Quite. Which aren't available for the Nokia patches, so pointing us
upstream is not the whole picture.

Cheers,

Andrew

-- 
Andrew Flegg -- mailto:andrew at bleb.org  |  http://www.bleb.org/

More information about the maemo-developers mailing list