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

From: Paul Klapperich maemo.org at bobpaul.org
Date: Tue Mar 27 18:22:25 EEST 2007
On 3/27/07, Neil MacLeod <gmane at nmacleod.com> wrote:
> Jakub.Pavelek at nokia.com wrote:
> > Hi all,
> >
> > This sounds like something technically easy to do (for Nokia):
> > 1) get all the internal bugs we have fixed
> > 2) extract the referrences to public bugzilla
> > 3) make sure all the public bugzilla bugs are marked as FIXED the same
> > day we release the update
> >
> > And as a bonus lets list the public bugs in the changelog as fixed. This
> > all should be done automatically, perhaps even for the 3.2007.10-7 so
> > that we do not forget about it next time again.
> >
> Hi Jakub
> That's exactly what I would hope for, and we can then VERIFY those bugs
> that have been FIXED (for example, bug 990[1] is supposed to have been fixed
> but is still present in 3.2007.10-7).
> Detailing internal bug fixes would be a bonus, simply because known
> problems don't always have a corresponding public bug, but I can appreciate
> this may be more difficult to extract and publish without incurring the
> wrath of management.

I think the ideal situation would be if the public bugzilla was used by
Nokia when fixing bugs submitted publicly and the internal bugzilla used
when fixing bugs Nokia feels need to be hidden from public view for whatever
reason. Actually, ideally the public bugzilla was the only bug listing, but
I know some components can't be open sourced. However, I believe bugzilla
allows access controls to particular bugs. I seem to remember the Mozilla
foundation marking bugs as "private" such that only the title of the bug was
publicly viewable as they pertained to major security holes. Perhaps down
the road something like this could be done? Or maybe some sort of automated
import/export between the public and private bugzilla?

I assume the reason the public bugzilla doesn't seem to get updated is that
the bugs are actually worked on using the internal bug tracker and it's
inconvenient to put the same messages in the internal and external tracker.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-developers/attachments/20070327/321e2c24/attachment.htm 
More information about the maemo-developers mailing list