Bug Tracker

Bug Tracker

[Stanley F.]

Good evening,

I'm interested in working for git during this year's GSoC program.
So I want to get familiar with the git code by implementing some
patches. But I can't find a bug tracker or something where are some
TODOs to prepare for GSOC.
Where can I find some small tasks, I can start with to get a reference
for my proposal?

Best regards
Stanley

Re: Bug Tracker

[Nguyen Thai Ngoc Duy]

On Sat, Mar 26, 2011 at 7:07 AM, Stanley F. <wurfk3ks@googlemail.com> wrote:
> Good evening,
>
> I'm interested in working for git during this year's GSoC program.
> So I want to get familiar with the git code by implementing some
> patches. But I can't find a bug tracker or something where are some
> TODOs to prepare for GSOC.
> Where can I find some small tasks, I can start with to get a reference
> for my proposal?

Git list is the bug tracker (well, not exactly a bug tracker). I wish
we have a todo list too. In the mean time you can look for "low
hanging fruit" in the list archive. I found this one:

http://marc.info/?l=git&m=129986810306332
-- 
Duy

Bug tracker

[Marco Gerards]

Hi,

It seems important to me to use a bugtracker.  We talked a bit about
it on IRC, but IIRC there was no outcome (or I forgot).  I do not
really care what bugtracker I have to use (I am familiar with the one
on savannah, but I would prefer one with email support).

There are some bugs in GRUB 2, and i we don't keep track of them we
will forget about some of them.  I know about a few bugs, even in some
of the code I wrote.  I'd like to document these bugs until I have the
time to fix them.

Another reason why I want this is because I will check in the PPC port
of GRUB 2 tomorrow.  This still has some bugs, I want to document them
so testers will know about these problems (And I definitely want a lot
of people testing the code and reporting bugs :)).

If no one has an alternative, I suggest adding some categories to
savannah and that we use that.

Thanks,
Marco

Re: Bug tracker

[Yoshinori K. Okuji]

On Friday 19 March 2004 23:44, Marco Gerards wrote:
> It seems important to me to use a bugtracker.  We talked a bit about
> it on IRC, but IIRC there was no outcome (or I forgot).  I do not
> really care what bugtracker I have to use (I am familiar with the one
> on savannah, but I would prefer one with email support).

These are from my experience:

1. Once a bug tracker is chosen and used, it is not very easy to migrate 
to another, because the database cannot be moved (AFAIK, no bug tracker 
supports this feature), and the URL is recorded in many places, such as 
an old manual.

2. A bug tracker with rich features looks nice, but it's very difficult 
to maintain.

3. Integration of e-mail with a bug tracker is really problematic. The 
main cause of this is that the behavior of MUA varies from MUA to MUA.

So I think the oldest method is the best: just having a file named BUGS. 
If you want to refer to mails related to a bug, you can write a URL of 
the list archive. If you use YAML <http://yaml.org/> as the format, it 
would be easy to write a helper application for it.

What do you think?

Okuji

Re: Bug tracker

[Marco Gerards]

"Yoshinori K. Okuji" <okuji@enbug.org> writes:

> So I think the oldest method is the best: just having a file named BUGS. 
> If you want to refer to mails related to a bug, you can write a URL of 
> the list archive. If you use YAML <http://yaml.org/> as the format, it 
> would be easy to write a helper application for it.
>
> What do you think?

That is fine for me.  Do we keep changelogs for BUGS?

--
Marco

Re: Bug tracker

[Yoshinori K. Okuji]

On Sunday 21 March 2004 18:09, Marco Gerards wrote:
> That is fine for me.  Do we keep changelogs for BUGS?

It's not necessary, because the CVS does it instead of you. :)

Okuji

Re: Bug tracker

[Jeroen Dekkers]

On Sun, Mar 21, 2004 at 05:44:57PM +0100, Yoshinori K. Okuji wrote:
> So I think the oldest method is the best: just having a file named BUGS. 
> If you want to refer to mails related to a bug, you can write a URL of 
> the list archive. If you use YAML <http://yaml.org/> as the format, it 
> would be easy to write a helper application for it.
> 
> What do you think?

It's fine by me. I just quickly looked at YAML, but I'm not sure
whether we need that. For me, a file formatted according to Emacs
Outline Mode is actually enough.

-- 
Jeroen Dekkers