Re: Bugzilla bug tracking database for 2.5 now available.

[Andrew Morton <akpm@digeo.com>]

"Martin J. Bligh" wrote:
> 
> > While I have this on my mind I want to express this now since the
> > very first bug that hit my mailbox had this issue.
> >
> > I DO NOT want to be working on bugs on anything other than Linus's
> > actualy sources.  The first bug I got was a networking bug with
> > Andrew Morton's -mm patches applied.
> >
> > This isn't going to work if that is what people are going to be
> > allowed to do.
> >
> > I want to suggest that all reported bug in the database must be
> > reporducable with some release done by Linus or his BK sources.
> > And also that we can automatically close any BUG submissions that
> > have other patches applied.
> 
> Hmmm ... I'm not sure that being that restrictive is going to help.
> Whilst bugs against any randomly patched version of the kernel
> probably aren't that interesting, things in major trees like -mm,
> -ac, -dj etc are likely going to end up in mainline sooner or later
> anyway ... wouldn't you rather know of the breakage sooner rather
> than later?

Well for that particular tree, the diff from mainline is quite
small, and those diffs are avowedly experimental.  That's why
it exists - the get fresh code some testing and exposure.

So people will need to use their judgement as to whether the
problem is in 2.5.47, or in the -bk snapshot which was taken from
Linus, or in the -mm addons.

If in doubt, people should go for the mailing list first.   Because

a) the response time will be better
b) more people will see it
c) the owners of the add-on patches can screen it quickly.

But hey.  It's early days yet, and it is easy to overdesign this 
sort of thing.  I'd say just start using the thing, and adapt
the work processes later on, based on some experience.