2010/12/1 Pertti Kellomäki <[email protected]>:
> On 12/01/2010 10:50 AM, ext Andrew Flegg wrote:
>>
>> I'm happy for the WhizBang tester to file a bug against WhizBang - but
>> once it's identified it's applauncherd (either by a WhizBang developer
>> *or* an applauncherd developer), a minimal test case SHOULD be created
>> anyway to add to the automated unit test suite.
>
> This is indeed happening, and the test case is made public in the git
> repository at gitorious.
Cool, that's reassuring ;-)
> The original bug was reported in the internal bugzilla and marked as fixed
> there. But in order to sell our package update to MeeGo, we would need to
> create an artificial bug at BMC so that we could then close it in order to
> refer to it in the Changelog. This is what I meant by us not being treated
> as proper upstream. Try suggesting kernel developers or xorg developers
> that they would need to file bugs at bugs.meego.com [...]
Indeed. But then the upstreams you're referring to have public bug
trackers where the reasoning behind a change is linked to the
appropriate commits and the discussion can be seen on the bug.
However, effectively - with an internal bug tracker - "applauncherd"
is _almost_ closed "source". It's certainly not open or conducive to
outside developers/testers/contributors.
Consider the following change:
--------8<--------
- if (foo->blah) {
+ if (!foo->blah) {
do_thing();
}
-------->8--------
If the changelog says "Fix problem caused by incorrect testing of
'blah'. Fixes NB#123456" that doesn't help include other people in
future with applauncherd development, nor give an open audit trail.
If applauncherd is only ever going to be maintained by Nokia, using
the internal bug tracker is fine. But that situation is NOT in the
best interests of the MeeGo project; so the current guideline is
trying to force Nokia to act in an open way, rather than just throwing
source code out with a somewhat opaque changelog.
Cheers,
Andrew
--
Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/
Maemo Community Council member
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
