rename the URL for feedback to something more positive
Change-Id: Iea248eeb3c3eacf9b0f123daa52516f5c1f0259c
- ::rtl::OUString sURL("http://hub.libreoffice.org/file-a-bug/?version="; +
utl::ConfigManager::getAboutBoxProductVersion() +
+ ::rtl::OUString sURL("http://hub.libreoffice.org/send-feedbac
Florian Effenberger wrote
> Hello,
> we have received a voucher for the Amazon Cloud, and after playing with
> it for a while, I think it could be a good extension for our current
> infrastructure.
> [...]
> Anyone has already experience with using the Amazon Cloud for compiling?
Hi!
Mozilla mo
Michael Meeks-2 wrote
> + Tollef's great work (thanks to TDF funding) on bugzilla:
> +
> https://bugs.freedesktop.org/page.cgi?id=weekly-bug-summary.html
> + shows the QA heros: top bug closers, stats of opened / shut
> etc.
Hi!
Great to see useful pages already
V Stuart Foote wrote
> So having a bit of a chore when grabbing a stack trace in Windows.
> Application to use seems to be the Sysinternals (Microsoft TechNet)
> Russinovich & Cogswell developed Process Monitor utility. It will
> completely capture to log ALL system activity on a Windows OS.
> The
julien2412 wrote
> Also, I uploaded detailed reports, I meant all files concerned by cppcheck
> reports + index page with links on source files "htmlized"
> You'll find it there:
> http://serval2412.free.fr/cppcheck_reports.tar.bz2
> Just uncompress and browse
Hi!
Could this be placed at http://de
Hi!
Please explain little more the following:
jmadero wrote
> -Status clarification (New vs. Reopened)
> **Agreed: *Reopened should only be used if the bug is assigned
- often Reopened status is used by the Reporters when bug is marked as
INVALID, DUPLICATE or WFM, how this new policy will work
On Fri, May 25, 2012 at 12:03 PM, Petr Mladek - pmla...@suse.cz wrote:
>> but I am not sure if my WinDbg output is any good.
> It is probably less informative without the .pdb files. Anyway, I guess
> that your are on the right way.
As I wrote earlier I have pdb symbols and source links in the Win
On Fri, May 25, 2012 at 3:21 PM, Petr Mladek - pmla...@suse.cz wrote:
> We are already using Litmus and are going to migrate to Moztrap. Though,
> we are not familiar with the real processes that used in the Mozilla
> project.
> Do you have any experience with the Mozilla processes? Are you able to
bfo wrote
>
> As I wrote earlier I have pdb symbols and source links in the WinDbg
> outputs,
> but I am concerned about missing FAULTING_SOURCE_LINE and
> FAULTING_SOURCE_CODE sections.
>
I managed to receive outputs with FAULTING_SOURCE_CODE section just as i
julien2412 wrote
>
> Hello,
> Quite recently, an interesting bt has been published by "bfoman" about
> this bug (see https://bugs.freedesktop.org/attachment.cgi?id=62055) , here
> are the top lines :
>
Hi.
I just wanted to add, that if there is more I can do to debug it - I will do
it (like some
julien2412 wrote
>
> Quite recently, an interesting bt has been published by "bfoman" about
> this bug (see https://bugs.freedesktop.org/attachment.cgi?id=62055) , here
> are the top lines :
>
Also check updated bt at
https://bugs.freedesktop.org/attachment.cgi?id=62322
--
View this message in
Michael Meeks-2 wrote
>
> On Fri, 2012-05-25 at 11:35 -0700, bfo wrote:
>> I read that you have unused reporting tool in the codebase and plans
>> to bring it back to life. Without it do you know the top crashers?
> Not really; we rely on human bug filing and QA
Petr Mladek wrote
>
> If you prepare the pages and template and
> if it is easy to add new week, Michael might do it himself in the
> future.
>
Firefox team is using CreateBox Wiki Extension for minutes - check their
wiki page at https://wiki.mozilla.org/Platform#Meetings
> Yes, any help is
Hi.
Today I stumbled upon Thunderbird code coverage report
(http://people.mozilla.org/~jcranmer2/c-ccov/).
Did anyone make such report for LibreOffice codebase?
Best regards.
--
View this message in context:
http://nabble.documentfoundation.org/LibreOffice-code-coverage-tp3994901.html
Sent from
David Ostrovsky wrote
>
> just for the record: we turned on gerrit's bug-db-integration machinery
>
Hi.
I accidentally hovered mouse pointer over fdo#x in some commit today and
was surprised that it is linked. Cool that it is enabled. Is it possible to
underline it at all times and/or chang
Hi.
Microsoft Office Professional Plus 2013 Preview Evaluation is available for
download as MSI installer at
http://technet.microsoft.com/en-US/evalcenter/hh973391.aspx?wt.mc_id=TEC_114_1_5
(link at the bottom of the page). Windows 7, Windows 8, Windows Server 2008
R2 or Windows Server 2012 requir
julien2412 wrote
>
> There's a tracker about coverage, see
> https://bugs.freedesktop.org/show_bug.cgi?id=38840
> For the moment, no one seemed to be on it (perhaps I'm wrong).
>
Hi.
What a discovery! I have found some scripts already in the codebase
http://opengrok.libreoffice.org/xref/core/sal
John Smith wrote
>
> I have been playing around with the llvm/clang static source code
> analyzer (http://clang.llvm.org/get_started.html) for a while now, and
> thought it might be fun and beneficial to run the analyzer on the
> libreoffice ('master') source code. For those interested the result
Petr Mladek wrote
>
> Create the wiki pages about getting the windows
> backtrace.
>
Hi.
Draft is available at
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg.
LO Windows developers are asked to comment:
- what debug output do they actually need
- which additional WinDbg c
> The bibisect is only possible for Bugs which are reproducible under Linux,
> if Linux has already been excluded (maybe bug history or comments will
> contain required information) bibisecting will not be possible. But of
> course, you can use bibisect to find out whether the bug is reproducible
Joel Madero-2 wrote
>
> Version 2, changed orientation and tried to take comments into
> account. Let me know what you all think.
>
Hi.
This is a very nice workflow, but I have some questions:
- how you define "Bug prevent users from making professional quality work?"
Interoperability issues a
Jan Holesovsky wrote
>
> Hi,
> On 2012-06-16 at 02:22 -0700, bfo wrote:
> Not at all - it is even possible to generate a zipped installation, that
> would be just unpacked, and checked into git; ie. nothing really hard to
> do. But nobody has done that yet - are you interes
Petr Mladek wrote
>
>> I'd change the workflow a little bit by putting the obvious things at the
>> top:
>> - feature requests aka wishlist
> I do not have any strong opinion for this. I think that it is is good to
> be able to discuss features, so "enhancement" bugs in bugzilla might be
> usable
Hi.
There are bug reports on bugs.freedesktop.org imported from AOO which are in
RESOLVED FIXED state there. Patches are commited to AOO codebase for some of
them. LO devs should reinvent the wheel to fix a fixed issues (just like
this thread is all about)? This can impact improving LO quality. Any
Noel Grandin wrote
>
>> - zero tolerance policy for regression issues during development
>> - zero tolerance policy for crash issues during development
> People who advocate zero tolerance for such things are welcome to
> provide the time and financial resources necessary to achieve this.
>
Hi.
Michael Meeks-2 wrote
>
> On the other hand giving all developers the idea that
> testing / bug fixing can be endlessly deferred since we'll never release
> - is a really poor plan too; one aspect of that is that it's not fair on
> the people that work diligently to test and fix things so we can
Bjoern Michaelsen wrote
>
>> + want a hard-hacks query - with five hits
> We can give that a try, but thinking about it that is really easy abused
> when
> just triggering on a whiteboard keyword (as in: people adding it to their
> pet
> peeve bugs). If that happens, handing over a q
Michael Meeks-2 wrote
>
> I have a slide test-case here:
> http://users.freedesktop.org/~michael/test-docs/Balmer.ppt
> It has a number of images, and bullets (and marketing nonsense) in it.
> It loads and renders fine in 3.6.0 - but in master the majority of the
> text and images are
John Smith wrote
>
> Not a new report (yet), but the clang analyzer reports have found a
> permanent home at this location :
> http://dev-builds.libreoffice.org/clang_reports/
>
Hi!
This is great news. Hope this will allow to improve LO codebase in any way.
Anyone could comment the results of th
Michael Meeks-2 wrote
>
> Thanks ! :-) turns out it was a line we lost during some comment
> translation, luckily thanks to Tomaž - it was trivial to find the three
> day old commit that caused the issue & isolate it really fast :-)
> That's the joy of debugging regressions vs. master
Michael Stahl-2 wrote
>
>> Did anyone make such report for LibreOffice codebase?
> no, unfortunately we don't know how the unit test coverage ranks exactly
> on a scale from "far too low" to "infinitesimal" :-/
>
Hi.
Thanks to work of John Smith such report is available at
http://dev-builds.lib
John Smith wrote
>
> Anyway, the generated html report as it currently is can be found here :
> http://dev-builds.libreoffice.org/lcov_reports/
>
Hi.
Great work! I hope both reports will be generated regularly and help improve
quality of LO codebase.
Best regards.
--
View this message in cont
Michael Meeks-2 wrote
>
> it should be fixed in the next build iteration.
>
Hi.
Checked with:
LO 3.7.0.0.alpha0+
Build ID: 6737f12
Windows XP Professional SP3
Could not reproduce. All good.
Best regards.
--
View this message in context:
http://nabble.documentfoundation.org/master-regressi
jmadero wrote
>> My suspicion is that the other freedesktop projects would hate
>> that,
>> and that this is something that we'd need to share with them; making it
>> rather difficult to fix.
Hi.
This could be done on per project basis. Unfortunately with
Michael Meeks wrote
> Generally
jmadero wrote
> I think that
> recognizing who is QA and who isn't will become an issue.
Hi.
It would be possible to create QA Bugzilla group with special icon and then
add QA people as members. Icon would be displayed along Bugzilla nick then.
See 3.15.1:3 https://bugs.freedesktop.org/docs/en/ht
Michael Meeks-2 wrote
> On Fri, 2012-09-28 at 10:33 -0700, bfo wrote:
>> This could be done on per project basis. Unfortunately with
> Oh ! if we know that this is easy to turn on on a per product basis
> (ie. a simple bugzilla setting just for our product); then that is
&
John Smith wrote
> Hi,
> Here's a clang static source code analysis of the latest git sources :
> http://dev-builds.libreoffice.org/clang_reports/master~2012-11-04_17.27.13/
Hi!
Is it comparable with the previous one? Hope you will update lcov one too.
Any chances to have those two updated on a re
On Thu, 2012-05-10 at 12:13 +0200, Jesús Corrius wrote:
> In any case, the right way to do it would be to automatically generate
> all PDBs for each released version, for example in: solver\wntmsci.pro\pdb.
> Then we put those generated PDBs online at symbols.libreoffice.org.
>> I think first we sh
On Wed, May 23, 2012 at 3:11 PM, Petr Mladek - pmla...@suse.cz wrote:
> bfo.bugm...@spamgourmet.com píše v Pá 18. 05. 2012 v 22:22 +0200:
> > On Thu, 2012-05-10 at 12:13 +0200, Jesús Corrius wrote:
> > > In any case, the right way to do it would be to automatically generate
> > > all PDBs for each
On Wed, May 23, 2012 at 3:11 PM, Petr Mladek - pmla...@suse.cz wrote:
>> Please consider. Always you can ask the friendly guys at Mozilla how
>> to set this all up...
> Thanks for tip.
What a discovery! Seems like complete how to:
http://zenit.senecac.on.ca/wiki/index.php/Mozilla_Source_and_Symbol
40 matches
Mail list logo
