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

From: Daniel Stone daniel.stone at nokia.com
Date: Tue Mar 27 18:39:16 EEST 2007
On Tue, Mar 27, 2007 at 10:22:25AM -0500, ext Paul Klapperich wrote:
> 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?

Products don't exist before announcement by definition, so it's very
difficult to work in an environment where most every bug must be secret
by default (anything pertaining to particular unannounced features).
There's also the matter of managing what to report to: there would need
to be some kind of permissions per-product or so.

> 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.

You got it.  The majority of the bug work happens before product
release: going by what's in the changelogs, the external database has
roughly 2% of the bugs as the internal one.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.maemo.org/pipermail/maemo-developers/attachments/20070327/15aab66c/attachment.pgp 
More information about the maemo-developers mailing list