This is the mail archive of the
ecos-maintainers@sources.redhat.com
mailing list for the eCos project.
Re: Doc on How to submit patches
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Andrew Lunn <andrew dot lunn at ascom dot ch>
- Cc: Jonathan Larmour <jifl at ecoscentric dot com>,eCos Maintainers <ecos-maintainers at sources dot redhat dot com>
- Date: 03 Sep 2003 06:48:04 -0600
- Subject: Re: Doc on How to submit patches
- Organization: MLB Associates
- References: <3F5522F8.3030404@eCosCentric.com> <20030903123432.GK6488@biferten.ma.tech.ascom.ch>
On Wed, 2003-09-03 at 06:34, Andrew Lunn wrote:
> On Wed, Sep 03, 2003 at 12:08:40AM +0100, Jonathan Larmour wrote:
> > Nick and myself have been working on this:
> > http://ecos.sourceware.org/patches.html
> >
> > Comments? Corrections? Abuse?
>
> The component to use in Bugzilla is "Patches and Contributions". Im
> humming and harring as to if it would be better to use the component
> the major part of the patch is in. That way it automagically gets a
> default owner who we can point a finger at when the patch sits around
> for a while with nothing happening. If the owner is overloaded its his
> responsibility to then find another maintainer to take over the patch.
>
> It would be nice to add a state "Waiting for assignment" to bugzilla.
>
Isn't this just the "new" state? Once it has been looked at by
someone, it should then be assigned (as appropriate) and changed to
"assigned" or "needinfo".
We currently have too many bugs that are just left at "new" (some in
the old system were 3-4 years old!). I think they should be moved to
a working status as soon as possible and yes, I know, I'm at least
as guilty as anyone else in this regard.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates