Full Article Attached Another Round of 1.3 Candidate Builds

Tuesday March 11th, 2003

Several fixes have been applied to the 1.3 branch in the last few days and a new set of release candidates is now available. Get the complete details from Asa Dotzler and then grab a build to help with the testing effort.

#44 Re: Re: Re: What pisses me off ...

by asa <>

Wednesday March 12th, 2003 3:00 AM

You are replying to this message

Either it was a pain in the ass to maintain or it made other parts of the automation more difficult or both. I know that when we did have it it was intermittant and I probably got email on average once a week or from someone saying "talkback doesn't work in today's linux build. do something." I know I blew time on several occasions trying to figure out if talkback wasn't packaged with that particular build, was packaged but wasn't working, was working but not for that particular crash, etc. and I imagine folks in build got even more complaints. I don't know why it was a pain and I don't much care because I don't see any huge win in having it for the zipped builds. I remember vaguely sending an email saying "sure, kill it, we've got more important things to worry about" or something like that but I don't remember why it was so much trouble.

We have no shortage of milestone talkback reports on Linux. We could probably get by on half the reports we currently get and still be able to identify and fix every one of the topcrashers we currently identify with talkback. We're not going to open up any floodgates of new information by enabling it in the zipped builds.

That being said, it certainly wouldn't hurt to have talkback for zipped builds on linux. The more the merrier. There may be some bug that's hard to diagnose and the one person with good comments might just happen to be using zipped builds. If you're offering to fix and maintain that piece of the build/packaging system or can convince someone else to maintain it then I'm happy to do what I can to get it reviewed/approved (although I'm not technically capable of doing code review for it). But if it's a pita to keep it working and no one's interested in doing that then I'd rather it not be there at all then it be there only some of the time.