On Tuesday 07 December 2010, George Kiagiadakis wrote:
> On Tue, Dec 7, 2010 at 11:14 PM, Thiago Macieira wrote:
> > On Tuesday, 7 de December de 2010 21:53:57 Benoit Jacob wrote:
> >> 2010/12/7 Thiago Macieira :
> >> > How are you going to properly find the stack without debug symbols?
> >> >
>
On Wed, Dec 08, 2010 at 07:27:48PM -0800, Gary Greene wrote:
> You might want to look at
> http://code.google.com/appengine/articles/rietveld.html as it does a
> fairly good job, and has a decent command line tool.
>
give us something like github patch queues and we talk business.
hmm, maybe nokia
On 8 Dec 2010, at 8:55 AM, Thiago Macieira wrote:
> Em Terça-feira, 7 de Dezembro de 2010, às 11:22:47, Benoit Jacob escreveu:
>> *
>> 1. Issue tracker (Mozilla) vs. Mailing lists (KDE).
>>
>> KDE uses a Mailing list for most its development discussion, and only
>> uses trackers (bugzilla, r
[ Comments below, in line ]
On Wednesday 08 December 2010 at 12:54 pm, Aaron J. Seigo penned
about "Re: Thoughts from a former KDE, currently Mozilla developer"
> On Wednesday, December 8, 2010, Thiago Macieira wrote:
> > One feature missing in Bugzilla is proper rich form
On Wednesday, December 8, 2010, Thiago Macieira wrote:
> One feature missing in Bugzilla is proper rich formatting, like a wiki.
or threaded conversations. like a mailing list. :)
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE co
Em Quarta-feira, 8 de Dezembro de 2010, às 09:39:42, Benoit Jacob escreveu:
> > Also, with
> > enough debug symbols you won't be able to search for libGL anyway as
> > the backtrace has references to source files only.
>
> How do you think that debuggers know the file? I think they just use
> the m
Em Terça-feira, 7 de Dezembro de 2010, às 11:22:47, Benoit Jacob escreveu:
> *
> 1. Issue tracker (Mozilla) vs. Mailing lists (KDE).
>
> KDE uses a Mailing list for most its development discussion, and only
> uses trackers (bugzilla, reviewboard) for specific tasks (user bug
> reports, patch re
On Tue, Dec 7, 2010 at 3:01 PM, Thiago Macieira wrote:
> On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
>> So do crash reports now automatically land in a database that's easy
>> to do queries on? (See the web interface provided by Socorro)
>>
>> If I want to get a list of all KDE
2010/12/7 Andreas Pakulat :
> On 07.12.10 14:28:57, Benoit Jacob wrote:
>> If I want to get a list of all KDE crashes that happened in libGL.so*,
>> how do I go about that?
>
> Thats more a problem of the tool we're using to track bugs, there's no
> way to tell bugzilla that something is a backtrac
2010/12/8 Kevin Ottens :
>> For smaller commits, it seems reasonable to demand that they don't cause
>> regressions. For larger commits, it won't always be possible to test
>> sufficiently for regressions before committing - there may be too many
>> affected apps if a change is made in the librarie
On Wednesday 8 December 2010 15:09:38 David Jarvie wrote:
> On Wed, December 8, 2010 8:38 am, Kevin Ottens wrote:
> > On Wednesday 8 December 2010 02:51:46 Aaron J. Seigo wrote:
> >> On Tuesday, December 7, 2010, Benoit Jacob wrote:
> >> > *
> >> > 3. QA, Unit-testing, continuous testing (KDE:
2010/12/7 Aaron J. Seigo :
>> *
>> 2. Can one tell volunteers contributors what they should be working
>> on? (KDE: no, Mozilla: yes)
>
> a nice bit of philosophy. imho:
>
> should we communicate what is needed to be worked on? yes.
> should we make it "cool" to work on what is needed by offeri
On Wed, December 8, 2010 8:38 am, Kevin Ottens wrote:
> On Wednesday 8 December 2010 02:51:46 Aaron J. Seigo wrote:
>> On Tuesday, December 7, 2010, Benoit Jacob wrote:
>> > *
>> > 3. QA, Unit-testing, continuous testing (KDE: very little, Mozilla: a
>> > lot)
>> >
>> > Let's face it, KDE has a
On Wednesday 8 December 2010 02:51:46 Aaron J. Seigo wrote:
> On Tuesday, December 7, 2010, Benoit Jacob wrote:
> > *
> > 3. QA, Unit-testing, continuous testing (KDE: very little, Mozilla: a
> > lot)
> >
> > Let's face it, KDE has always been deficient in the QA department. In
> >
> > order
On Tuesday, December 7, 2010, Benoit Jacob wrote:
> Hi,
>
> I would like to share some hopefully interesting thoughts, from a
> comparison of a few things in KDE and in Mozilla, in the hope that it
> helps KDE borrow good ideas from elsewhere.
thanks :)
> *
> 1. Issue tracker (Mozilla) vs. M
On 07.12.10 14:28:57, Benoit Jacob wrote:
> 2010/12/7 Andreas Pakulat :
> > On 07.12.10 11:22:47, Benoit Jacob wrote:
> >> *
> >> 4. Crash reports handling (KDE: poor, Mozilla: good)
> >> * Have a look at Socorro, Mozilla's crash report tool:
> >
> > Your info is outdated I think, try out a KD
2010/12/7 Stephen Kelly :
> Benoit Jacob wrote:
>
>> Hi,
>>
>> I would like to share some hopefully interesting thoughts, from a
>> comparison of a few things in KDE and in Mozilla, in the hope that it
>> helps KDE borrow good ideas from elsewhere.
>>
>> *
>> 1. Issue tracker (Mozilla) vs. Mail
On Tuesday, 7 de December de 2010 22:39:21 Boudewijn Rempt wrote:
> I implemented a socorro server and integrated breakpad in the desktop app I
> developed at Hyves. It was rather frightening, especially to maintain. And
> it seemed to only work with binaries you create and distribute yourself --
>
On Tuesday 07 December 2010, Benoit Jacob wrote:
> 2010/12/7 Thiago Macieira :
> > On Tuesday, 7 de December de 2010 21:53:57 Benoit Jacob wrote:
> >> 2010/12/7 Thiago Macieira :
> >> > How are you going to properly find the stack without debug symbols?
> >> >
> >> > Imagine one frame that didn't k
On Tue, Dec 7, 2010 at 11:14 PM, Thiago Macieira wrote:
> On Tuesday, 7 de December de 2010 21:53:57 Benoit Jacob wrote:
>> 2010/12/7 Thiago Macieira :
>> > How are you going to properly find the stack without debug symbols?
>> >
>> > Imagine one frame that didn't keep the frame pointer properly?
2010/12/7 Thiago Macieira :
> On Tuesday, 7 de December de 2010 21:53:57 Benoit Jacob wrote:
>> 2010/12/7 Thiago Macieira :
>> > How are you going to properly find the stack without debug symbols?
>> >
>> > Imagine one frame that didn't keep the frame pointer properly?
>>
>> If the stack is damaged
Benoit Jacob wrote:
> Hi,
>
> I would like to share some hopefully interesting thoughts, from a
> comparison of a few things in KDE and in Mozilla, in the hope that it
> helps KDE borrow good ideas from elsewhere.
>
> *
> 1. Issue tracker (Mozilla) vs. Mailing lists (KDE).
Hi,
Are you sugg
On Tuesday, 7 de December de 2010 21:53:57 Benoit Jacob wrote:
> 2010/12/7 Thiago Macieira :
> > How are you going to properly find the stack without debug symbols?
> >
> > Imagine one frame that didn't keep the frame pointer properly?
>
> If the stack is damaged, then indeed I can't do anything;
2010/12/7 Thiago Macieira :
> On Tuesday, 7 de December de 2010 21:13:53 Benoit Jacob wrote:
>> 2010/12/7 Thiago Macieira :
>> > On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
>> >> So do crash reports now automatically land in a database that's easy
>> >> to do queries on? (See the
On Tuesday, 7 de December de 2010 21:13:53 Benoit Jacob wrote:
> 2010/12/7 Thiago Macieira :
> > On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
> >> So do crash reports now automatically land in a database that's easy
> >> to do queries on? (See the web interface provided by Socorro
2010/12/7 Benoit Jacob :
> 2010/12/7 Thiago Macieira :
>> On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
>>> So do crash reports now automatically land in a database that's easy
>>> to do queries on? (See the web interface provided by Socorro)
>>>
>>> If I want to get a list of all
2010/12/7 Thiago Macieira :
> On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
>> So do crash reports now automatically land in a database that's easy
>> to do queries on? (See the web interface provided by Socorro)
>>
>> If I want to get a list of all KDE crashes that happened in lib
On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
> So do crash reports now automatically land in a database that's easy
> to do queries on? (See the web interface provided by Socorro)
>
> If I want to get a list of all KDE crashes that happened in libGL.so*,
> how do I go about that?
On Tuesday 07 December 2010 20:28:57 Benoit Jacob wrote:
> 2010/12/7 Andreas Pakulat :
> > On 07.12.10 11:22:47, Benoit Jacob wrote:
> >> *
> >> 4. Crash reports handling (KDE: poor, Mozilla: good)
> >
> >> * Have a look at Socorro, Mozilla's crash report tool:
> > Your info is outdated I thi
2010/12/7 Andreas Pakulat :
> On 07.12.10 11:22:47, Benoit Jacob wrote:
>> *
>> 4. Crash reports handling (KDE: poor, Mozilla: good)
>> * Have a look at Socorro, Mozilla's crash report tool:
>
> Your info is outdated I think, try out a KDE 4.5 app crashing. Dr.Konqi
> improved a _lot_ in the l
On 07.12.10 11:22:47, Benoit Jacob wrote:
> *
> 4. Crash reports handling (KDE: poor, Mozilla: good)
> * Have a look at Socorro, Mozilla's crash report tool:
Your info is outdated I think, try out a KDE 4.5 app crashing. Dr.Konqi
improved a _lot_ in the last year or so and its being actively
> 4. Crash reports handling (KDE: poor, Mozilla: good)
To be clear, I know about Dr Konqi but afaics it relies on the user to
install debug symbols by himself, that's unrealistic. The symbols
lookup needs to be done server-side if you want this to work on a
large scale with non-technical users.
B
Hi,
I would like to share some hopefully interesting thoughts, from a
comparison of a few things in KDE and in Mozilla, in the hope that it
helps KDE borrow good ideas from elsewhere.
*
1. Issue tracker (Mozilla) vs. Mailing lists (KDE).
KDE uses a Mailing list for most its development discu
33 matches
Mail list logo
