From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE Bugzilla Future
Date: Fri, 11 Mar 2011 16:27:08 +0000 [thread overview]
Message-ID: <4D7A4D5C.8060106@xora.org.uk> (raw)
In-Reply-To: <4D7A422C.9010003@mentor.com>
On 11/03/2011 15:39, Tom Rini wrote:
> On 03/11/2011 03:00 AM, Graeme Gregory wrote:
>> On 11/03/2011 08:19, Stefan Schmidt wrote:
>>> Comments? Volunteers?
>>>
>> Is there any newer bug tracking systems which should be considering?
>>
>> If we keep bugzilla then we are still running a system where people do
>> everything twice. They email patches to OE mailing list for review and
>> also have to file them into bugzilla. If we could somehow combine the
>> two functions. Effectively integrate patchwork and bug tracker into one
>> system. I have no idea if such a bug tracker exists.
>>
>> Also I might suggest we shift to launchpad or another hosted solution.
>> That way we can lesson the load on the admin team.
>>
>> Im happy to step up and be a bug massager if we decide to run with a
>> bugtracker, but I think we need to decide if that is the correct
>> workflow for us first.
>
> FWIW, I've become a fan of JIRA, but only as a user / project admin,
> haven't admined the server itself.
>
I admin the server and being in Java its really easy. The last update
cycle even seperated the data from server code so switching versions
became even easier.
All your test data is held in SQL database and attachments on disk.
The real magic though is maintainer fixing the workflow
(new->accepted->blah->fixed) which someone else did.
Graeme
next prev parent reply other threads:[~2011-03-11 16:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 8:19 OE Bugzilla Future Stefan Schmidt
2011-03-11 9:05 ` Koen Kooi
2011-03-11 10:17 ` Stefan Schmidt
2011-03-11 12:17 ` Koen Kooi
2011-03-11 10:00 ` Graeme Gregory
2011-03-11 14:38 ` Philip Balister
2011-03-11 15:27 ` Eric Bénard
2011-03-11 15:39 ` Tom Rini
2011-03-11 16:27 ` Graeme Gregory [this message]
2011-03-11 18:05 ` Otavio Salvador
2011-03-11 22:01 ` Khem Raj
2011-03-17 18:10 ` Michael 'Mickey' Lauer
2011-03-17 21:14 ` Richard Purdie
2011-03-18 7:57 ` Frans Meulenbroeks
2011-03-18 10:15 ` Phil Blundell
2011-03-19 1:03 ` Richard Purdie
2011-03-19 8:28 ` Frans Meulenbroeks
2011-03-20 16:02 ` Philippe De Swert
2011-03-20 18:18 ` Khem Raj
2011-03-20 21:08 ` Frans Meulenbroeks
2011-03-21 1:24 ` Khem Raj
2011-03-21 10:08 ` Richard Purdie
2011-03-21 12:33 ` Frans Meulenbroeks
2011-03-21 2:14 ` Tom Rini
2011-03-21 3:24 ` Khem Raj
2011-03-21 8:23 ` Koen Kooi
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=4D7A4D5C.8060106@xora.org.uk \
--to=dp@xora.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.