From: Vitus Jensen <vjensen@gmx.de>
To: openembedded-devel@openembedded.org
Subject: Re: Bugtracker Status
Date: Fri, 23 Jan 2009 08:27:40 +0000 (UTC) [thread overview]
Message-ID: <glbv1s$au0$1@ger.gmane.org> (raw)
In-Reply-To: 87wscmn8ne.fsf@neumann.lab.ossystems.com.br
Am Thu, 22 Jan 2009 22:55:17 -0200 schrieb Otavio Salvador:
> "Michael 'Mickey' Lauer" <mickey@vanille-media.de> writes:
>
>> Hi guys,
>>
>> we have 1141 open bugs in the bugtracker, a couple of hundreds from
>> ancient autobuilder builds, some more hundreds application specific
>> bugs, and then some actual ones.
>>
>> I think there are two ways to deal with the mess:
>>
>> 1.) Officially close the bugtracker down.
>>
>> 2.) Attack the situation.
>>
>> I'm fine with either way, though if we'd go for 2.), I'd propose:
>>
>> 2.1.) Removing all autobuilder bugs completely (how can we script
>> that?) and stop autobuilder automatically adding bugs. It was a great
>> idea, but it didn't work out. We do not have enough manpower and it
>> just messes up the bugtracker.
>> 2.2.) Remove all software specific bugs that have an upstream and are
>> not distribution-relevant, such as GPE, Opie, Kernel, etc. 2.3.)
>> Reinstate the monthly bug squashing weekends.
>>
>> Opinions?
>
> 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)
...
While I just occasional work with OpenEmbedded I have to remark that I
have two patches patches published which didn't make it into the
repository the last months:
1. posted to this list (adds htmldoc)
2. in bugzilla (fixes php 5 compile)
I can live with that, just using my private branch. But having gotten no
comments what's wrong with those patches I think this shows that either
way doesn't work at the moment.
And --- if you want my opinion --- it's much easier for me to monitor my
comments in bugzilla or search patches there.
By[t]e,
Vitus
--
Vitus Jensen, Hannover, Germany, Earth, Milky Way, Universe (current)
next prev parent reply other threads:[~2009-01-23 8:35 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 [this message]
2009-01-23 10:30 ` Valentin Longchamp
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='glbv1s$au0$1@ger.gmane.org' \
--to=vjensen@gmx.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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