Re: bugzilla process for submitting fixes
On Thu, 2003-11-20 at 14:01, Alan Coopersmith wrote: Is there some way to mark a newly filed bug so it's clear that there's a patch attached and it just needs to be reviewed and checked in? According to the bugzilla docs, FIXED means the code is checked in and there doesn't seem to be any Fix Provided state other than NEW. It's not clear to me there's any way other than manual review of NEW bugs to determine which ones need time spent debugging and fixing, and which ones just need to be reviewed and committed, but it would seem if we could mark bugs like that when submitting the patches, the people who do the reviews and commits could more easily get through them without wading through those they don't have the time to try to fix themselves at the moment. (Maybe changing it to be assigned to [EMAIL PROTECTED] instead of developers or something like that would work.) One could use the Keywords field (which XFree86 Bugzilla doesn't seem to have), e.g., Keywords: INCLUSION. This could require an upgrade of Bugzilla, I'm no expert. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
bugzilla process for submitting fixes
Is there some way to mark a newly filed bug so it's clear that there's a patch attached and it just needs to be reviewed and checked in? According to the bugzilla docs, FIXED means the code is checked in and there doesn't seem to be any Fix Provided state other than NEW. It's not clear to me there's any way other than manual review of NEW bugs to determine which ones need time spent debugging and fixing, and which ones just need to be reviewed and committed, but it would seem if we could mark bugs like that when submitting the patches, the people who do the reviews and commits could more easily get through them without wading through those they don't have the time to try to fix themselves at the moment. (Maybe changing it to be assigned to [EMAIL PROTECTED] instead of developers or something like that would work.) -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc.- Sun Software Group User Experience Engineering: G11N: X Window System ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: bugzilla process for submitting fixes
put [PATCH] in the bug description maybe? Alex --- Alan Coopersmith [EMAIL PROTECTED] wrote: Is there some way to mark a newly filed bug so it's clear that there's a patch attached and it just needs to be reviewed and checked in? According to the bugzilla docs, FIXED means the code is checked in and there doesn't seem to be any Fix Provided state other than NEW. It's not clear to me there's any way other than manual review of NEW bugs to determine which ones need time spent debugging and fixing, and which ones just need to be reviewed and committed, but it would seem if we could mark bugs like that when submitting the patches, the people who do the reviews and commits could more easily get through them without wading through those they don't have the time to try to fix themselves at the moment. (Maybe changing it to be assigned to [EMAIL PROTECTED] instead of developers or something like that would work.) -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc.- Sun Software Group User Experience Engineering: G11N: X Window System __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: bugzilla process for submitting fixes
On Thu, Nov 20, 2003 at 11:01:49AM -0800, Alan Coopersmith wrote: Is there some way to mark a newly filed bug so it's clear that there's a patch attached and it just needs to be reviewed and checked in? According to the bugzilla docs, FIXED means the code is checked in and there doesn't seem to be any Fix Provided state other than NEW. It's not clear to me there's any way other than manual review of NEW bugs to determine which ones need time spent debugging and fixing, and which ones just need to be reviewed and committed, but it would seem if we could mark bugs like that when submitting the patches, the people who do the reviews and commits could more easily get through them without wading through those they don't have the time to try to fix themselves at the moment. I've never seen a good answer to this one. If I were submitting patches, I'd be discussing them here. It is usually a good idea to do that anyway, regardless of the patch submission mechanisms. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: bugzilla process for submitting fixes
On Thu, Nov 20, 2003 at 02:06:16PM -0800, Alan Coopersmith wrote: I'm getting ready to submit an XDMCP/IPv6 patch as soon as I finish testing it that will change the default IPv6 multicast address to the one IANA finally assigned after we decided to go ahead and start the standards public review without waiting for it. I don't think there's much there worth discussing, but would like to see it in the 4.4 release so it doesn't go out with a different multicast group address than everyone else (and presumably later XFree releases) will be using. Send a copy here as soon as you have a version ready for review. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
