On Thu, Jun 5, 2014 at 7:08 PM, Jay Philips wrote:
> Hi All,
>
> The bug reporter of 79599 has done all the ground work and would like to
> submit some code, so if someone from the devs could nudge him in the
> right direction.
Hi Jay,
The more programmers, the merrier! I'd point anyone interest
On Thu, Jun 5, 2014 at 6:36 PM, Jay Philips wrote:
> Hi All,
>
> I submitted my first windows and linux backtraces today to fdo#79569,
> and would love feedback on it so i know i've done it right. On the linux
> site, i noticed that when i run 'soffice --backtrace', one of the lines
> that it outp
Hi Brian,
Sorry for the long delay - not sure if someone else already responded.
Chrome is giving a false positive - it's a bug on there side. You can
force the download (or download using a different browser) and
everything will work fine.
Best,
Joel
P.S. Thanks so much for the donation - is n
Hi All,
The bug reporter of 79599 has done all the ground work and would like to
submit some code, so if someone from the devs could nudge him in the
right direction.
--
Regards,
Jay Philips
___
List Name: Libreoffice-qa mailing list
Mail address: Lib
Hi All,
I submitted my first windows and linux backtraces today to fdo#79569,
and would love feedback on it so i know i've done it right. On the linux
site, i noticed that when i run 'soffice --backtrace', one of the lines
that it outputs is "Reading symbols from
/opt/libreoffice4.2/program/soffic
Hi Joren,
Looking over keywords, you are correct that it has 'have-backtrace', it
even has 'want-backtrace', and it also has keywords that arent that
useful in the keyword field like bibisected (used in WhiteBoard),
NEEDINFO (used in status), and notourbug (used in status).
Regards,
Jay Philips
Joel Madero schreef op 5/06/2014 17:26:
Ah I didn't see that. We should change it to camel case to be
consistent. HaveBacktrace. Will include on whiteboard page.
Just to be sure: have-backtrace is a keyword and our key words are not
camel-cased ;-). We may want to consider to make it more cons
On 06/05/2014 05:36 AM, Joren DC wrote:
> Hi,
>
> Jay Philips schreef op 5/06/2014 4:45:
>> I think it might be a good idea to include the following whiteboard
>> keywords -
>>
>> HasDebug or HasBacktrace & HasStrace - When the bug reporter or
>> commenter has included the backtrace or strace outp
Crap I see ;) Thanks - we can talk about consistency between keyword and
whiteboard once we actually get our own instance of bugzilla :)
Best,
Joel
On 06/05/2014 08:29 AM, Joren DC wrote:
>
> Joel Madero schreef op 5/06/2014 17:26:
>>
>> Ah I didn't see that. We should change it to camel case to
On 06/05/2014 05:36 AM, Joren DC wrote:
> Hi,
>
> Jay Philips schreef op 5/06/2014 4:45:
>> I think it might be a good idea to include the following whiteboard
>> keywords -
>>
>> HasDebug or HasBacktrace & HasStrace - When the bug reporter or
>> commenter has included the backtrace or strace outp
* Present
+ Cloph, David, Eike, Fridrich, Michael M, Stephan, Thorsten, Ptyl, Miklos
Kendy, Markus, Bjoern, Robinson, Michael S, Caolan, Andras, floeff, Jacobo
* Completed Action Items
+ talk to distro vendors wrt. commit access setup (Michael)
+ crashtest box - more research (M
Hey Xisco,
> Hello all,
>
> does it make sense to include another status for the regression issues
> where the problematic commit has been identified ? I'm asking it
> because yesterday I spent some time on this task and I could chase
> down two regressions, one of them made by a Collabora develop
On Thu, 2014-06-05 at 16:07 +0200, Bjoern Michaelsen wrote:
> Hi,
>
> On Thu, Jun 05, 2014 at 09:06:07AM -0400, Kohei Yoshida wrote:
> > So, to me personally, this practice of "witch-hunting" (or
> > finger-pointing) really bogs me down, especially I receive such notice
> > hundreds of times durin
Hi,
On Thu, Jun 05, 2014 at 09:06:07AM -0400, Kohei Yoshida wrote:
> So, to me personally, this practice of "witch-hunting" (or
> finger-pointing) really bogs me down, especially I receive such notice
> hundreds of times during a typical development cycle.
There is no witch-hunting in this and le
On Thu, 2014-06-05 at 15:41 +0200, Joren DC wrote:
> Hi Kohei,
>
> Kohei Yoshida schreef op 5/06/2014 15:06:
> > So, to me personally, this practice of "witch-hunting" (or
> > finger-pointing) really bogs me down, especially I receive such notice
> > hundreds of times during a typical development
Hi *,
A new version of the LibreOffice Impress Remote for Android has been
uploaded to Google play
https://play.google.com/store/apps/details?id=org.libreoffice.impressremote
If you don't want to use google play (or cannot), you can sidelode the
remote via
http://downloadarchive.documentfoundatio
Hi Kohei,
Kohei Yoshida schreef op 5/06/2014 15:06:
So, to me personally, this practice of "witch-hunting" (or
finger-pointing) really bogs me down, especially I receive such notice
hundreds of times during a typical development cycle.
Well, that's at least not what I'm talking about right now.
Hi all,
The tag sdremote-2.1.1 (aka v11) has been created in the
impress_remote repository.
https://gerrit.libreoffice.org/gitweb?p=impress_remote.git;a=summary
It is a minor update to the previous version that includes updated
translations and action-bar buttons to turn on/off the
pointer-featur
On Thu, 2014-06-05 at 14:42 +0200, Joren DC wrote:
> Hi Xisco, *,
>
> Xisco Faulí schreef op 5/06/2014 10:32:
> > does it make sense to include another status for the regression issues
> > where the problematic commit has been identified ? I'm asking it
> > because yesterday I spent some time on
> HasDebug or HasBacktrace & HasStrace - When the bug reporter or
> commenter has included the backtrace or strace output, so devs can
> easily see this list
Please consolidate on ONE of those before introducing this and viciously kill
the others. "have-backtrace" looks find to me and is a registe
Hi,
Jay Philips schreef op 5/06/2014 4:45:
I think it might be a good idea to include the following whiteboard
keywords -
HasDebug or HasBacktrace & HasStrace - When the bug reporter or
commenter has included the backtrace or strace output, so devs can
easily see this list
I didn't invent it, b
Hi Xisco, *,
Xisco Faulí schreef op 5/06/2014 10:32:
does it make sense to include another status for the regression issues
where the problematic commit has been identified ? I'm asking it
because yesterday I spent some time on this task and I could chase
down two regressions, one of them made
On Thu, Jun 5, 2014 at 11:56 AM, klaus-jürgen weghorn ol
wrote:
> Hi Christian,
>
> no Winnies:
> http://dev-builds.libreoffice.org/pre-releases/win/
uups, sorry. didn't check whether the upload was actually done when
sending, just did look at the estimate when I started uploading - but
in the me
Hi Cloph,
Le 05/06/2014 11:50, Christian Lohmaier a écrit :
> Hi *,
>
> for the upcoming new version 4.3.0 the builds for Beta2 are now
> available on pre-releases. (some windows helppacks still uploading)
>
> It is a LibreOfficeDev build, meaning that it won't replace your
> stable version of Li
Hi all,
Thanks for the great QA Meeting. Meeting minutes are available here:
https://wiki.documentfoundation.org/QA/Meetings/2014/June_04
Our next meeting will be in two weeks on June 18th (17:30 UTC). Please
feel free to add new items to the agenda here:
https://wiki.documentfoundation.org/QA/Me
Hi Christian,
no Winnies:
http://dev-builds.libreoffice.org/pre-releases/win/
Am 05.06.2014 11:50, schrieb Christian Lohmaier:
Hi *,
for the upcoming new version 4.3.0 the builds for Beta2 are now
available on pre-releases. (some windows helppacks still uploading)
It is a LibreOfficeDev buil
Hi all,
The tag libreoffice-4.3.0.0.beta2-buildfix1 (AKA 4.3.0 Beta2) has been
created on the libreoffice-4-3 brannch.
The branch will be used for fine tuning of the 4.3 codeline.
See
https://wiki.documentfoundation.org/ReleasePlan/4.3#4.3.0_release for
the detailed schedule of the 4.3.0 release
Hi *,
for the upcoming new version 4.3.0 the builds for Beta2 are now
available on pre-releases. (some windows helppacks still uploading)
It is a LibreOfficeDev build, meaning that it won't replace your
stable version of LibreOffice, but can be installed alongside
LibreOffice 4.2
Also note that
Hello all,
does it make sense to include another status for the regression issues
where the problematic commit has been identified ? I'm asking it because
yesterday I spent some time on this task and I could chase down two
regressions, one of them made by a Collabora developer ( I've already sent
29 matches
Mail list logo
