[oe] Bugtracker Status
Koen Kooi
k.kooi at student.utwente.nl
Fri Jan 23 07:55:22 UTC 2009
On 23-01-09 01:55, Otavio Salvador wrote:
>
> I propose to change the workflow a bit (and reuse few points you've proposed):
>
> 1. stop using bugtracker to handle patches
> 2. use mailing list to handle patches (comments bellow)
> 3. drop autobuilder bug reporting (comments bellow)
I agree on all points, I have been advocating 2) for a long time :)
regards,
Koen
> Besides, I have no objection about your points 2.2 and 2.3 but I'm too
> new in the OE environment to comment about them so let me comment
> about my points:
>
> 1 and 2:
>
> We're trying to get more people to review the changes to be done in
> OE dev tree and bugzilla UI is horrible and difficult to use (at
> least for me). Most people ends up redoing someone else patch since
> we don't watch carefully the bugtrack.
>
> I propose we move to mailing list reviewing process mostly like Linux
> kernel does. We can use PatchWork (http://ozlabs.org/~jk/projects/patchwork/)
> tool to make our life easier. I see some pros for that:
>
> . people will get more review into the patches
> . people will be aware of ongoing work and what is being prepared to
> be merged
> . less forgotten patches
> . less duplicated work
>
> I also see a single con for that:
>
> . more mailing list traffic
>
> 3:
>
> Instead of reporting bugs, we could mail mailing list with the
> failure and link a log for someone to take a look. It makes us to
> worry more about the change since if we break something _everyone_
> we'll know it :-)
>
> My 2c :P
>
More information about the Openembedded-devel
mailing list