From: Valentin Longchamp <valentin.longchamp@epfl.ch>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: Bugtracker Status
Date: Fri, 23 Jan 2009 11:30:08 +0100 [thread overview]
Message-ID: <49799C30.90508@epfl.ch> (raw)
In-Reply-To: <87wscmn8ne.fsf@neumann.lab.ossystems.com.br>
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)
>
> 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
>
Even if I am not very much involved in the OE development, I completely
agree with Otavio. The few patches that I have proposed are often stuck
on the bugzilla. Maybe it would be better with a mailing-list.
Furthermore, now that we use git, we have plenty of tools to send
patches to a mailing-list (format-patch, send-email and am).
I would definitely support a patch review style like on the linux kernel
mailing-lists even if this implies a high-traffic list (with simple
filter rules in your mail client, it's easy to handle). However, I don't
think it would be a good idea to have two lists.
My 2 c.
Val
--
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne
next prev parent reply other threads:[~2009-01-23 10:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 0:31 Bugtracker Status Michael 'Mickey' Lauer
2009-01-23 0:55 ` Otavio Salvador
2009-01-23 1:39 ` Philip Balister
2009-01-23 1:49 ` Otavio Salvador
2009-01-23 1:51 ` Otavio Salvador
2009-01-23 3:16 ` Khem Raj
2009-01-23 7:55 ` Koen Kooi
2009-01-23 13:36 ` Florian Boor
2009-01-23 13:59 ` Marcin Juszkiewicz
2009-01-23 8:27 ` Vitus Jensen
2009-01-23 10:30 ` Valentin Longchamp [this message]
2009-01-23 11:06 ` Mailinglists, was: " Koen Kooi
2009-01-23 12:00 ` Petr Stetiar
2009-01-23 15:36 ` Chris Larson
2009-02-05 14:06 ` Koen Kooi
2009-02-05 21:29 ` Roman I Khimov
2009-02-11 12:45 ` Koen Kooi
2009-02-11 12:51 ` Koen Kooi
2009-02-11 13:20 ` Philip Balister
2009-02-11 17:19 ` Otavio Salvador
2009-02-11 18:15 ` Bernhard Guillon
2009-02-13 20:56 ` Rodrigo Vivi
2009-02-11 13:40 ` Sledz, Steffen
2009-02-24 9:20 ` Martyn Welch
2009-02-24 16:11 ` Michael 'Mickey' Lauer
2009-02-24 16:51 ` Koen Kooi
2009-02-24 18:09 ` Andrea Adami
2009-01-23 13:20 ` Florian Boor
2009-02-17 16:55 ` Rolf Leggewie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49799C30.90508@epfl.ch \
--to=valentin.longchamp@epfl.ch \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox