[Libreoffice] communicating bugs found in build form master

Cor Nouws oolst at nouenoff.nl
Wed Aug 10 15:40:40 PDT 2011

Hi Kohei,

Kohei Yoshida wrote (10-08-11 16:21)
> On Wed, 2011-08-10 at 15:44 +0200, Cor Nouws wrote:
>> A.  If I find an issue, is it OK if I mail this list or just ping on IRC?
>> Just to prevent adding bugs that are already noticed (not in bugzilla)
>> and maybe even fixed in master after I udated?
> So, I'm not a big fan of cluttering bugzilla with bugs in master
> *unless* the bug stays there for weeks and you already know who to
> assign to (to have the bug report serve as a reminder for that person to
> fix later).

Since my irregular presence here/work with master builds, that is hard 
to achieve...

> But I'm not strongly against this.

Ah, glad to read that ;-)

> Also, sometimes we notice that something is broken on master and
> fix it immediately in a few days.

Yes, so maybe it is better if I just drop my finding on IRC, and only if 
no one recognises it, make an issue.

> The better thing to do is to narrow down the commits that may have
> broken it if you know the last commit that worked.  If you are willing,
> you could even take advantage of git bisect to achieve this, in theory.

"git bisect " ... Thanks for the tip. I hope others taka advantage, for 
me it sounds as something for later.

>> e.g. I wrote https://bugs.freedesktop.org/show_bug.cgi?id=39979
>> but can on the other hand hardly imagine that it hasn't been tracked
>> already..
> I saw Miklos and Caolan discussing something like this today on IRC.
> Not sure if it's the same thing or not.

Indeed, was that.

Thanks for your help :-)

  - Cor
  - http://nl.libreoffice.org

More information about the LibreOffice mailing list