Re: [Evolution-hackers] Patch Review process
- From: Elijah Newren <newren gmail com>
- To: JP Rosevear <jpr novell com>
- Cc: evolution-hackers lists ximian com, gnome bugzilla hackers <bugzilla-devel-list gnome org>, Harish Krishnaswamy <kharish novell com>, gnome-bugsquad gnome org
- Subject: Re: [Evolution-hackers] Patch Review process
- Date: Mon, 9 May 2005 09:50:33 -0600
On 5/9/05, JP Rosevear <jpr novell com> wrote:
> On Mon, 2005-05-09 at 20:05 +0530, Harish Krishnaswamy wrote:
> > hi All,
> >
> > During the irc meeting last week, we discussed the pros and cons of
> > deprecating evolution-patches and using bugzilla as the treasure
> > bag for patches.
> >
> >
> > A quick recap of the main points in favor of Bugzilla -
> > * we tend to 'lose' patches in e-p. Bugzilla is more sticky.
> > * easier for downstream packagers to release updates.
> > * b.g.o can be queried for un/reviewed patches.
> >
> > the other side of the coin :
> > * bgo is much slower than reading mails
> > * you need to be on-line to pull down the patches.
> >
> > Fresh thoughts, any ?
>
> Yes. The ideal way might be to use bugzilla for patches and see if we
> could get automated mails to e-p containing the bug number, product,
> component and summary (and a link) if a patch is attachment is set on a
> bug.
Sounds somewhat similar to the automated patch-nagging we were
planning on doing (though that was more aimed at patches that had been
in bugzilla for a long time without being reviewed, but I'm sure the
same code could be used to do something like this). I think this
sounds reasonable.
Elijah
[Date Prev][
Date Next] [Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]