Windows BuildBot [was: Re: [RELEASE]: AOO 4.1.1 milestone 3, based on rev. 1612804]

[Oliver-Rainer Wittmann]

Hi,

On 24.07.2014 16:31, Pedro Lino wrote:

Hi Juergen, all

Already installed and ran (and confirmed/tested previous bugs)
It is working perfectly (at least the en_US version)

I'm a little worried that the Windows Nightly based on the same build failed
http://ci.apache.org/builders/aoo-win7/builds/99



The logs from #99 are already overriden by logs from #100. The logs from 
#100 showed me that there seems to be "no space left on the device"


Thus, it seems to be an error of build machine.

Best regards, Oliver.


Is this bad news or it is not a problem?

Regards,
Pedro


On Thu, Jul 24, 2014 at 2:51 PM, Jürgen Schmidt 
wrote:


That means m3 will become a new revision. More info later ...


ok the upload is nearly finished and the rebuild me is based on revision
1612804.

Available as always under

https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds
when the upload is complete. try again later if you should have problems.





-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [RELEASE]: AOO 4.1.1 milestone 3, based on rev. 1611634

[Oliver-Rainer Wittmann]

Hi,

On 21.07.2014 18:03, Jürgen Schmidt wrote:

Hi,

the translation deadline was last Friday and the milestone 3 build is
underway.

The m3 build is based on revision 1611634 from AOO410 branch. I have
integrated 12 translation updates (including new languages). We have
updates for de, he, km, lt, pl, pt, th, vi, zh-TW and new languages are
ca, ca-XV and ca-XR.

An overview of the fixed issues since AOO 4.1 can be found under
http://ci.apache.org/projects/openoffice/milestones/4.1.1-m3-r1611634/AOO4.1.1_fixes.html

The upload of the binaries builds is ongoing and can be found under
https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds

Happy testing and verifying of fixed issues. Feedback is welcome as
reported issues or discussion on our d...@openoffice.apache.org mailing list.



A serious defect has found its way into recent code line of planned 
4.1.1 release - see issue 125299, also reported on the verification of 
issue 125228.


This means that many text documents given in the Open Document Format 
(ODF) will cause a crash during import.


I already found the defect cause and will provide a fix today.

Best regards, Oliver.

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [REQUEST] help needed on newly submitted issues

[Oliver-Rainer Wittmann]

Hi,

On 01.07.2014 23:26, Kay Schenk wrote:

On Tue, Jul 1, 2014 at 1:39 AM, Oliver-Rainer Wittmann <
orwittm...@googlemail.com> wrote:


Hi,

in order to assure that we address the serious defects in our planned
4.1.1 release I would like to request help on newly submitted issues.

My issue query for issues which had been submitted since our 4.1.0 release
and which are not solved contain more than 200 issues. Most of them are in
status unconfirmed and several of them have subjects which indicate that
they are critical.

In order to support the developers it would be really great, if these
issues could be reviewed:
- check, if the issue can be reproduced --> status confirmed
-- if not reproducible, ask for more information --> keyword needmoreinfo
- check, if the issue is a duplicate --> resolve as duplicate
- check, if the issue is a regression to a recent release - e.g. no defect
in 4.0.0 or/and 4.0.1, but not in 4.1.0 --> adjust version field
- give attention to issues which seem to be serious enough to be
considered for the next release.

Thanks in advance,
Oliver.



Do you have a public saved search for this or should we just reference the
BZ messages to dev since the 4.1.0 release?



I have no public saved query, but you can use the following URL.
It is long as it contain all the search criteria which I am using and 
thus reflects my perferences for such a view on these issues:


https://issues.apache.org/ooo/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ACCEPTED&bug_status=REOPENED&chfield=[Bug%20creation]&chfieldfrom=2014-04-28&chfieldto=Now&columnlist=product%2Ccomponent%2Cversion%2Ckeywords%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate&f1=cf_bug_type&f2=product&f3=product&f4=version&known_name=OpenSubmittedSince410&list_id=153560&o1=equals&o2=notequals&o3=notequals&o4=notsubstring&query_based_on=OpenSubmittedSince410&query_format=advanced&v1=DEFECT&v2=Infrastructure&v3=Build%20Tools&v4=4.2.0


Best regards, Oliver.

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

[REQUEST] help needed on newly submitted issues

[Oliver-Rainer Wittmann]

Hi,

in order to assure that we address the serious defects in our planned 
4.1.1 release I would like to request help on newly submitted issues.


My issue query for issues which had been submitted since our 4.1.0 
release and which are not solved contain more than 200 issues. Most of 
them are in status unconfirmed and several of them have subjects which 
indicate that they are critical.


In order to support the developers it would be really great, if these 
issues could be reviewed:

- check, if the issue can be reproduced --> status confirmed
-- if not reproducible, ask for more information --> keyword needmoreinfo
- check, if the issue is a duplicate --> resolve as duplicate
- check, if the issue is a regression to a recent release - e.g. no 
defect in 4.0.0 or/and 4.0.1, but not in 4.1.0 --> adjust version field
- give attention to issues which seem to be serious enough to be 
considered for the next release.


Thanks in advance,
Oliver.

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: Goodbye

[Oliver-Rainer Wittmann]

Hi Edwin,

On 06.05.2014 12:29, Andrea Pescetti wrote:

Edwin Sharp wrote:

I encounter arrogance and aggression which I despise, and therefore
decided to quit volunteering.


This is totally unexpected.

Everybody despises arrogance and aggression as much as you, so we will
definitely get rid of them instead of seeing an important contributor
like you leave.

Do you have some links to Bugzilla/lists where something has gone wrong?
Give us some context and I'm sure that the project will be taking all
actions you need to be able to continue contributing in a pleasant
environment.



I can only second the Andrea's statements.

If you want you can provide more context via priv...@openoffice.apache.org.


Best regards, Oliver.

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [VOTE]: Release Apache OpenOffice 4.1.0 (RC2)

[Oliver-Rainer Wittmann]

Hi,

On 09.04.2014 09:04, Oukcha oukcha wrote:

2014-04-09 8:09 GMT+02:00 Edwin Sharp :


-1
Issue 124607 Linux x86-64 DEB: 1585426 not OK, 1585624 OK.


I confirm crash (issue 124607) on Xubuntu x64 with AOO410m15(Build:9761)

-  Rev. 1585426



It reveals that the installation packages for Linux systems do not 
contain the fix for issue 124607 due to some building issue.


Herbert is rebuilding the installation sets for Linux systems.


Best regards, Oliver.

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [RELEASE]: propose AOO 4.1.0 RC - Showstoppers?

[Oliver-Rainer Wittmann]

Hi,

On 06.04.2014 16:26, Rob Weir wrote:

On Sun, Apr 6, 2014 at 2:18 AM, Oliver-Rainer Wittmann
 wrote:

Hi,


On 06.04.2014 09:06, Rainer Bielefeld wrote:


Hi,

we have a potential showstopper Issue 124607 - .odt with (Page-No) field
in header/footer and comment for text range fails to open with "Read
Error. Error reading file"
<https://issues.apache.org/ooo/show_bug.cgi?id=124607>



For me it is a show-stopper.

I propose to prepare a new RC which includes a corresponding fix.
The fix is already in progress.



Hi Oliver,

Could you say a few words about the defect.  Did it exist in the beta as well?



Yes, it is in the code since 2013-12-19

Best regards, Oliver.


-Rob


Best regards, Oliver.




CU

Rainer

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [RELEASE]: propose AOO 4.1.0 RC - Showstoppers?

[Oliver-Rainer Wittmann]

Hi,

On 06.04.2014 09:06, Rainer Bielefeld wrote:

Hi,

we have a potential showstopper Issue 124607 - .odt with (Page-No) field
in header/footer and comment for text range fails to open with "Read
Error. Error reading file"




For me it is a show-stopper.

I propose to prepare a new RC which includes a corresponding fix.
The fix is already in progress.

Best regards, Oliver.



CU

Rainer

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: OpenOffice Beta writer 4.1 and NVDA's Say All Feature

[Oliver-Rainer Wittmann]

Hi,

On 03.04.2014 17:55, David Goldfield wrote:

I’m wondering if someone else who is using the NVDA screen reader could
confirm the following issue.
NVDA has a command which allows the user to hear the contents of the
entire document from the cursor position to the end of the file, unless
the control key is pressed to silence the speech.  This key, by default,
is insert-down arrow.  For folks who aren’t familiar with screen
readers, the insert key on the numeric keypad is often used as a
modifier key, just as we often use keys such as the alt or control keys
to perform specific functions when combined with other keys.  Pressing
the insert key along with the down arrow is NVDA’s continuous read
command. Make sure numlock is turned off.
With OpenOffice Beta Writer, NVDA seems to stop reading after a few
lines.  I’m guessing this is an NVDA issue and, if it is, I will see if
a ticket has been filed on their bug tracker regarding the problem.  If
it has not, I’ll report it.
If, for some reason, the issue is with OO I wanted to let someone know
about it in case it can be fixed by an OO developer.



I am not sure, if the following has impact on NVDA document reading 
function.
As far as I remember only the visible part of a text document in Writer 
is available to AT tools via the accessibility API. Thus, it might be 
that NVDA just read the text which it could retrieve from OpenOffice Writer.


Could you check, if NVDA reads all the visible text and then stops?

Best regards, Oliver.


/*David Goldfield*/
*Computer Technology Instructor*
*919 Walnut Street*
*4th Floor*
*Philadelphia, PA  19107*
*215-627-0600 ext 3277*
*FAX:  215-922-0692*
*dgold...@asb.org* **
*www.asb.org* 
Serving Philadelphia’s and the nation’s blind and visually impaired
population since 1874.
www.asb.org
www.asb.org




-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: Bug Wrangler Heroes

[Oliver-Rainer Wittmann]

Hi,

On 18.03.2014 16:26, Rob Weir wrote:

On Wed, Mar 12, 2014 at 4:41 AM, Rainer Bielefeld
 wrote:

Hi all,

May be you are interested to know how who are the most active bug wranglers
in Bugzilla?

Because my scripting skills are not very good I used AOO Calc to find out
with following steps (something "quick and dirty"):



We should think of what stats we want.  I can help with scripting it in Python.

1) Maybe a monthly summary, count of new bugs, closed bugs, etc.,
categorized by product.  Also total comments, count of volunteers
contributing.

2) Highlight the bugs with most activity that month

3) Volunteers with most new bug reports

4) Volunteers with most comments/activity



0
Downloaded<https://mail-archives.apache.org/mod_mbox/openoffice-issues/201402.mbox>
1   Copied to a .csv
2   opened document in AOO Calc
3   Filtered for "--- Comment #" to find comment headings
4   Copied visible rows to new sheet
5   Deleted all until "From": Regular expressions find ".*from"
 and replace with nothing
6   Delete anything behind name: Regular expressions find "<.*"
 and replace with nothing
7   Copy to new table and sort
8   Filter for "not empty – no duplicates"
9   Behind every visible contents "=COUNTIF(A$1:A$3000;A1)"
 (Example for row 1)counts number of duplicates
10   Copy to empty text documents and replace
  tabulators by blanks for posting here

The result (only contributors with more than 3 comments) for February 2014:

Comments / Name
-------
824   Edwin Sharp
294   Rainer Bielefeld
174   Armin Le Grand
142   Oliver-Rainer Wittmann
126   SVN Robot
089   Andre
051   hanya
041   h...@apache.org
041   j...@apache.org ---
035   Marcus
035   Regina Henschel
034   Ariel Constenla-Haile
025   j.nitsc...@ok.de ---
023   zhaoshzh
022   Sam Jennings
018   V Stuart Foote
017   fanyuz...@gmail.com ---
016   Andrea Pescetti
016   Thorsten Wagner
015   brinzing
014   liuping
013   Clarence GUO
012   jolatt
012   Rob Weir
011   aterb...@progressive.com ---
011   Yuri Dario
010   bmarcelly
010   kurt.pfei...@gmail.com ---
009   Kevin Chilton
009   lauhub
009   r...@apache.org ---
007   gvalla...@gmail.com ---
007   oooforum
007   Raphael Bircher
007   richlv
007   snoff
006   Apostolos Syropoulos
006   behnoosh
006   hhu...@gmail.com ---
006   jmpoo
006   John
006   Shenfeng Liu
006   slacka
005   Aivaras Stepukonis
005   Andreas S=C3=A4ger
005   annette_ciancibe...@progressive.com ---
005   beckyfiedler
005   digulla
005   ella_no...@progressive.com ---
005   Jon Peli Oleaga
005   JP CASSOU
004   Akriti
004   bnjroo
004   hbie...@gmail.com ---
004   Kay
004   Kim Tidwell
004   laura h
004   Oukcha
004   schlocke
004   SharPorz
004   Sreedevi
004   sworddragon
004   trebly
004   veathako

Some more statistics for February:
-
2513  Comments
  180  Commenters



I'm getting different results, though using a Python script, perhaps
with different assumptions.

I took all the posts from the February mbox for
iss...@openoffice.apache.org.  I rejected ones that were release
blocker processing issues, the ones starting with "review" or
"4.1.0_release_blocker" in the subject.

For the remaining I looked at the "X-Bugzilla-Who" header to get the
name of the person who changed the BZ issue.

This gives me 3295 changes, from 228 people, more than what you have.
My top 10 list is:

el...@apache.org: 1020
rainerbielefeld_ooo...@bielefeldundbuss.de: 406
o...@apache.org: 212
armin.le.gr...@me.com: 175
svn...@dev.null.org: 126
awf@googlemail.com: 108
mar...@apache.org: 90
h...@apache.org: 79
j...@apache.org: 62
hanya.r...@gmail.com: 51

Maybe I'm counting more than comments and new issue reports?  What
changes do not require a comment?  Changing the priority of an issue,
for example?


Often, I add myself to or remove myself from CC without any comment.
For my review of issues fixed for AOO 4.1.0 I also just changed the 
Target Milestone field.


Just my observations.

Best regards, Oliver.



Regards,

-Rob


Problems:

New reports are not in the statistics, not a real problem, but my time was
too limited. Hope I did not integrate too many fallacies into my
calculations ;-)

Best regards

Rainer

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: Read Error in when ms document (docx) open in OO

[Oliver-Rainer Wittmann]

Hi Akriti,

thanks for the screen shots.

Now, I figured out that you did not meant a read error on the file 
itself, but a read error on an embedded graphic.


In the meanwhile I reproduced the read error on the embedded graphics 
with the developer snapshot from 2014-01-13 (rev. 1556251)


In the new developer snapshot this defect has been fixed - see Bugzilla 
issue 123723 [1].


Please try the new developer snapshot, announced today by Herbert.


[1] https://issues.apache.org/ooo/show_bug.cgi?id=123723


Best regards, Oliver.


On 27.01.2014 15:31, akriti wrote:

Hello Mr Wittmann,

Please have a look on attached screenshot

Thanks & Regards,
Akriti Jaiswal


On 27 January 2014 19:40, Oliver-Rainer Wittmann
mailto:orwittm...@googlemail.com>> wrote:

Hi,


On 25.01.2014 18:03, akriti wrote:

Hello Yuzhen,

I would like to inform you that the the snapshots present in
attached doc
of  test case AOO TEST 99 got a 'Read Error ' when opened in OO.
eg: in Story2973&2023-ModifyExist-__TableStyles.dcx

Hence the execution of the mentioned  testcase is blocked.
Please confirm
whether this is a valid issue.


I could not reproduce the 'Read Error' in the developer snapshot on
Windows 7 announced today by Herbert.
The document opens fine in this version.

I will check also the developer snapshot from 2014-01-13. I will
report my results in a couple of minutes.

Best regards, Oliver.



Thanks & Regards,
Akriti Jaiswal


--__--__-
To unsubscribe, e-mail: qa-unsubscribe@openoffice.__apache.org
<mailto:qa-unsubscr...@openoffice.apache.org>
For additional commands, e-mail: qa-h...@openoffice.apache.org
<mailto:qa-h...@openoffice.apache.org>




-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: Read Error in when ms document (docx) open in OO

[Oliver-Rainer Wittmann]

Hi,

On 25.01.2014 18:03, akriti wrote:

Hello Yuzhen,

I would like to inform you that the the snapshots present in attached doc
of  test case AOO TEST 99 got a 'Read Error ' when opened in OO.
eg: in Story2973&2023-ModifyExist-TableStyles.dcx

Hence the execution of the mentioned  testcase is blocked. Please confirm
whether this is a valid issue.



I could not reproduce the 'Read Error' in the developer snapshot on 
Windows 7 announced today by Herbert.

The document opens fine in this version.

I will check also the developer snapshot from 2014-01-13. I will report 
my results in a couple of minutes.


Best regards, Oliver.



Thanks & Regards,
Akriti Jaiswal



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [QA][Test Report] Weekly Status Update as of 20140117

[Oliver-Rainer Wittmann]

Hi,

Thanks for report.
I have some comments/questions - see inline below.

On 17.01.2014 13:27, Yuzhen Fan wrote:

Hi All,
We started doing the AOO 4.1 Function Verification test(FVT), here is the
weekly update (1/13 - 1/17):

*Test execution:*
1.  New feature testing on comments/Annotations on text ranges - Ongoing
Bugs found: (red one is critical)
Bug 124030 - Failed to open ODT file exported from AOO with
comment/annotation in original docx file (fix submitted by Oliver, will
verify with next build)


This one is already fixed.


Bug 124028 - Highlight of commented/annotated text range gets lost when
export as PDF by AOO


An improvement/change to the PDF export is needed. Currently, 
comments/annotations are exported as "PDF Sticky Notes" which do not 
offer the feature to be applied to a text range. Instead it would make 
sense to export such comments/annotations as "PDF Highlight Text". For 
this deeper knowledge on the PDF file format is needed.



Bug 124027 - The list numbers/bullets in comment/annotation get lost when
import .docx file to AOO


This issue is not related to the improvement "comments/annotations on 
text ranges".




2.  Improved feature testing on In-place editing of Input Fields - Complete
Bugs found:
Bug 123827- [Accessibility][IA2]Focus value of Field function type list
can't be identified in writer
Bug 123828 - [Accessibility]Tab Key can't travel in input field dialogue in
writer
Bug 123825 - The content change when importing .docx with “Date" field


This issue has been closed approx. two weeks ago as NOT_AN_ISSUE.
Why is it nevertheless reported here?


Bug 123826 - The content lost when importing .docx with “Fill-in" field


This issue is not related to the improvement "in-place editing of Input 
Fields". It had been reported two weeks ago that it already occurs in 
released version 4.0.1 (today, I confirmed that it reproducible also in 
OOo 3.2.0 and OOo 3.3.0).
Why is it reported in context of the improvement "in-place editing of 
Input Fields"?




3. Existing feature on 3 APP testing - Ongoing
We have assigned 287 text executions to about 5 volunteers, and completed
about 13.8% in execution (150 test executions done). We are far from and
tight to finish feature FVT before Feb 13 with current resource. I have
sent 2nd call for volunteers in community.


 TotalNot RunPassedFailedBlockedCompleted [%]
Debian Linux 64bit5673610387.5
MacOS X20918515908.13
Redhat Linux 32bit69670202.90
Redhat Linux 64bit2222193001.35
Ubuntu Linux 64bit1671652001.20
Windows 71801253817231.67
Windows 818216911207.14
Total108593710540513.8

*Defect summary:* see above bug lists in Test execution

*Issues & quality highlight:*
1. We have execution gap in FVT test as lack volunteers in testing, have
sent the 2nd call for volunteers
2. Build for Mac 64bit is not available in buildbot and dev snapshot
3. Build for Linux is not available in dev snapshot


There are Linux 32bit deb-packages available on the snapshot - see 
http://ci.apache.org/projects/openoffice/#linsnap



Best regards, Oliver.



*Volunteer status: *
1. No new volunteers(total 5 so far) on FVT execution work, 2 person(Edwin
and Liu Ping) ask for more as they have completed their assignment

*Plan for next week:*
1. Continue to do FVT test on Mac, Linux and Windows
2. Continue to do testing on comments/Annotations on text ranges
3. Summarize high priority issues in Bugzilla

Thanks you all for effort this week, let's continue and make progress next
week!

Regards,
Yu Zhen



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: Call for volunteera for AOO in-place editing of Input Fields Testing in Writer

[Oliver-Rainer Wittmann]

Hi,

as the developer of this changes I am also available for questions, 
comments, improvements, criticsm.


The task to provide an appropriate Release Notes entry for this changes 
is also open. Thus, feedback for the corresponding wiki page is also 
welcome as it could be the source for the Release Notes entry.


Best regards, Oliver.

On 13.12.2013 05:51, Liu Ping wrote:

Hi,Maryna

Welcome to your participation , let me know if you have any question.
If it is possible ,you may post your testing status or testing result in
mail
Thanks your efforts



On Thu, Dec 12, 2013 at 9:13 PM, Maryna Martynenko wrote:


Hi Liu Ping,


I can test on the following platforms: Windows 8, Ubuntu .

Regards,
Maryna.


On Mon, Dec 9, 2013 at 5:41 AM, Liu Ping  wrote:


Hi,

Solution for issue 33737 [1] successfully integrated with trunk as rev
1543006 (Build download: http://ci.apache.org/projects/openoffice/)

We need volunteers to support testing work, including Windows/Linux/Mac
platform， hope to finish testing in 1~2 weeks

We focus on two fields: *Text Input Fields*, *User Variable Input

Fields* ,

no changes are made for
*Simple Variable Input Fields *

According by Oliver-Rainer's wiki[2] , *Basic Points:*

- Edit content of Input Fields


- Enter/Leaving Input Fields


- Traveling between Input Fields


- Selection of Input Fields


- No Field Names for Input Fields


- Microsoft Word binary filter (WW8 filter)


- Documents in read-only mode

you also refer Areas which need high attention during testing in wiki[2]
[1] https://issues.apache.org/ooo/show_bug.cgi?id=33737
[2] https://wiki.openoffice.org/wiki/Writer/Input_Fields<
https://wiki.openoffice.org/wiki/Writer/Input_Fields>

If you are interested in this testing project,  please follow up this

mail

and let us know your testing status
Thanks you all for effort







-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [VOTE]: Release Apache OpenOffice 4.0.1 (RC3)

[Oliver-Rainer Wittmann]

Hi,

On 25.09.2013 12:17, Yuzhen Fan wrote:

-1:

I vote -1 for RC3 because of these 3 issues, the first two are function
regressions from 3.4.1 and 4.0.0, the last one is for bad user experience
on Redhat 64bit installation.

Bug 123345 - [Regression]Docx embedded table display incorrectly
Bug 123346 - [Regression]the bullet display incorrectly when open docx file
in AOO
Bug 123348 - Cannot integrate AOO 4.0.0 in desktop menu in Redhat6.4 64bit



I can confirm that 123345 and 123346 are regressions which had been 
introduced in AOO 4.0.0


On the one hand I agree that regressions introduced in the latest 
release should be fixed in the next release.
On the other hand we are already quite far in our planned AOO 4.0.1 
release schedule and AOO401rc3 contains a lot of important bug fixes and 
improvements regarding our supported languages. Thus, I strongly vote 
for releasing AOO401rc3 as AOO 4.0.1 under these circumstances.
From my point of view 123345 and 123346 should be release blocker for 
our next release.


Regarding issue 123348:
As far as I know this issue is not new and already known. I think a 
workaround exist. Thus, for me this is not a release blocker.


Yu Zhen, do you think you can change your mind regarding your vote?


Best regards, Oliver.



Regards,
Yu Zhen


On Wed, Sep 25, 2013 at 4:07 PM, Herbert Duerr  wrote:


this is a call for vote on releasing the RC3 release candidate as

Apache OpenOffice 4.0.1. This will be an important update release for
Apache OpenOffice 4.0 to fix some serious regressions and to introduce
some new languages (Basque, Khmer, Lithuaian, Polish, Serbian Cyrillic,
Swedish, Turkish, Vietnamese and Chinese Traditional). It is a further
key milestone to continue the success of OpenOffice.
[...]

The RC is based on the release branch AOO401, revision 1524958!

Please vote on releasing this package as Apache OpenOffice 4.0.1.
[...]

 [ ] +1 Release this package as Apache OpenOffice 4.0.1
 [ ]  0 Don't care
 [ ] -1 Do not release this package because...



+1 : release AOO401rc3 (a.k.a. r1524958) as Apache OpenOffice 4.0.1

Herbert



--**--**-
To unsubscribe, e-mail: 
dev-unsubscribe@openoffice.**apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org






-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: Triage for AOO 4.0.0 Release Blockers

[Oliver-Rainer Wittmann]

Hi,

On 22.06.2013 09:55, Oliver-Rainer Wittmann wrote:

Hi,

Am 20.06.2013 um 17:09 schrieb Oliver-Rainer Wittmann 
:


Hi,

On 06.06.2013 13:54, Yuzhen Fan wrote:

Hi All,

Here is the list of identified candidates[1]/[2] which are proposed to
be 4.0.0 release blockers. Please indicate your selections for release
blockers by giving 1 vote to 1 bug (the vote field is beside the
importance field, in a bug form). We hope to get the vote score this
week, any bugs you think most critical to you, please bring out and
let's discuss.

[1]
https://issues.apache.org/ooo/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=4.0.0_release_blocker%3F&sharer_id=249289&list_id=64740
[2] Also attach the file for the list
(AOO4.0.0_release_blocker_candidates.ods)


Armin, Jürgen, Andre and myself reviewed in the last days the list of issues 
which had been requested for release blocker (release blocker flag = '?') and 
are not solved.

We propose the following issues as release blockers [1]:
- 120250
- 120443 (actually 121772 - 120443 is a dup. of this one)
- 120513
- 120559
- 121008
- 121143
- 121256
- 121435


Has been fixed in the meanwhile. Thus, it can removed from the list.


This statement is only meant for 121435
just to avoid unambigious interpretation ;-)

Best regards, Oliver.



Best regards, Oliver.


- 121479
- 121751
- 121925
- 121968
- 121977
- 122163
- 122300

Any objections to mark these issues as release blocker?

[1] 
https://issues.apache.org/ooo/buglist.cgi?quicksearch=120250%20120443%20120513%20120559%20121008%20121143%20121256%20121435%20121479%20121751%20121925%20121968%20121977%20122163%20122300%20121772&list_id=68303


Best regards, Oliver.


-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: Triage for AOO 4.0.0 Release Blockers

[Oliver-Rainer Wittmann]

Hi,

Am 20.06.2013 um 17:09 schrieb Oliver-Rainer Wittmann 
:

> Hi,
> 
> On 06.06.2013 13:54, Yuzhen Fan wrote:
>> Hi All,
>> 
>> Here is the list of identified candidates[1]/[2] which are proposed to
>> be 4.0.0 release blockers. Please indicate your selections for release
>> blockers by giving 1 vote to 1 bug (the vote field is beside the
>> importance field, in a bug form). We hope to get the vote score this
>> week, any bugs you think most critical to you, please bring out and
>> let's discuss.
>> 
>> [1]
>> https://issues.apache.org/ooo/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=4.0.0_release_blocker%3F&sharer_id=249289&list_id=64740
>> [2] Also attach the file for the list
>> (AOO4.0.0_release_blocker_candidates.ods)
> 
> Armin, Jürgen, Andre and myself reviewed in the last days the list of issues 
> which had been requested for release blocker (release blocker flag = '?') and 
> are not solved.
> 
> We propose the following issues as release blockers [1]:
> - 120250
> - 120443 (actually 121772 - 120443 is a dup. of this one)
> - 120513
> - 120559
> - 121008
> - 121143
> - 121256
> - 121435

Has been fixed in the meanwhile. Thus, it can removed from the list.

Best regards, Oliver.

> - 121479
> - 121751
> - 121925
> - 121968
> - 121977
> - 122163
> - 122300
> 
> Any objections to mark these issues as release blocker?
> 
> [1] 
> https://issues.apache.org/ooo/buglist.cgi?quicksearch=120250%20120443%20120513%20120559%20121008%20121143%20121256%20121435%20121479%20121751%20121925%20121968%20121977%20122163%20122300%20121772&list_id=68303
> 
> 
> Best regards, Oliver.

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: Triage for AOO 4.0.0 Release Blockers

[Oliver-Rainer Wittmann]

Hi,

On 21.06.2013 08:57, Jürgen Schmidt wrote:

On 6/20/13 8:01 PM, Edwin Sharp wrote:

Yes. please allow to share the following objections: 1. in general,
bugs shouldn't be rated


I disagree here and you always rate issues starting with setting a
priority. And as always you can't fix them all with a fix number of
developers. It simply doesn't work. That means you have to
prioritize and that is quite normal.


2. most are crashes - "release blocker" can be other than crash -
i.e. copy chart from Calc into Writer results in chart area without
curve. this is a huge bug that doesn't involve a crash

exactly and we have defined some criteria for issues, crashes, data
loss and security issues have always high priority. Regressions are
also very important especially when often used functionality is
broken.

It is documented in the wiki but I haven't the reference in place
yet, have to look for it.


3. with all the respect to Norwegian users, print dialog too wide
is a negligible problem

not for this specific user group and the fix is already available.


4. there should be a documented evidence to the bug evaluation
process, based on approved SOP

I am not sure if I understand you here


5. the general public has no declared release date - no need to
rush as there is no commitment to fulfill

no but the project have committed to a release date and I believe
the majority of the community support the new release. You have to
set a date and have define what is important for this date. You can
always do more and can fix more issues but that won't work very
well.


6. "minor" bugs should also get attention and be targeted

definitely but not short in front of a release. And of course nobody
prevent anybody from fixing such issues. We have a lot of them, many
are probably not longer valid and can be closed, other are not easy
to fix and so on. A good start would be of course to simply check
older issues if they are still valid or not.


7. the judgment of introducing the sidebar with so many pending
bugs should be justified to demonstrate openness

as far as I know we haven't pending bugs here. Don't mix this up
with improvement or feature requests. Maybe I don't understand you
and you can explain it again


8. RTF is rarely used today - no reason for two appearances in the
list

RTF is as far as I known relevant for Ms interoperability in general
and important for other MS filters as well. Even the pure format is
not used often the functionality is important. If somebody knows more
please correct me.


Just some more background on the RTF filter:
The RTF format is used on copy-and-paste actions between OpenOffice
applications and other applications.
For example, issue 120023 is caused by a defect in the RTF filter.


Best regards, Oliver.


9. Are there no "critical" bugs in Math, Draw and Base?

probably yes and probably many other critical bugs in other areas
that are not detected yet or not proposed as showstopper


10. Are there enough volunteers to treat these "release blockers"
on time?

we hope we can fix them all but volunteers are never enough ;-)

If you think that other issue should be showstopper as well, please
propose them on the dev list and we can discuss them. That's the way
how we want to handle it

Further discussion should take place on the dev list


Juergen



Thank you



On Thu, Jun 20, 2013, at 18:09, Oliver-Rainer Wittmann wrote:

Hi, Any objections to mark these issues as release blocker?

[1]
https://issues.apache.org/ooo/buglist.cgi?quicksearch=120250%20120443%20120513%20120559%20121008%20121143%20121256%20121435%20121479%20121751%20121925%20121968%20121977%20122163%20122300%20121772&list_id=68303





Best regards, Oliver.


-



To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org

For additional commands, e-mail: qa-h...@openoffice.apache.org



-



To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org

For additional commands, e-mail: qa-h...@openoffice.apache.org




-



To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org

For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: Triage for AOO 4.0.0 Release Blockers

[Oliver-Rainer Wittmann]

Hi,

On 06.06.2013 13:54, Yuzhen Fan wrote:

Hi All,

Here is the list of identified candidates[1]/[2] which are proposed to
be 4.0.0 release blockers. Please indicate your selections for release
blockers by giving 1 vote to 1 bug (the vote field is beside the
importance field, in a bug form). We hope to get the vote score this
week, any bugs you think most critical to you, please bring out and
let's discuss.

[1]
https://issues.apache.org/ooo/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=4.0.0_release_blocker%3F&sharer_id=249289&list_id=64740
[2] Also attach the file for the list
(AOO4.0.0_release_blocker_candidates.ods)



Armin, Jürgen, Andre and myself reviewed in the last days the list of 
issues which had been requested for release blocker (release blocker 
flag = '?') and are not solved.


We propose the following issues as release blockers [1]:
- 120250
- 120443 (actually 121772 - 120443 is a dup. of this one)
- 120513
- 120559
- 121008
- 121143
- 121256
- 121435
- 121479
- 121751
- 121925
- 121968
- 121977
- 122163
- 122300

Any objections to mark these issues as release blocker?

[1] 
https://issues.apache.org/ooo/buglist.cgi?quicksearch=120250%20120443%20120513%20120559%20121008%20121143%20121256%20121435%20121479%20121751%20121925%20121968%20121977%20122163%20122300%20121772&list_id=68303



Best regards, Oliver.

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [AOO 4.0]: migration of AOO 3.4.x/OOo 3.x user profile data - help needed

[Oliver-Rainer Wittmann]

Hi

On 28.05.2013 17:10, Oliver-Rainer Wittmann wrote:

Hi,

I would like to activate/introduce code which migrates certain user
profile data from AOO 3.4.x and OOo 3.x installations during the
reactivated FirstStartWizard when the user starts the first time an
installed AOO 4.0.
I have submitted two issues for this task:
- 122398 for the reactivation of the FirstStartWizard [1]
- 122397 for the code and configuration changes to migrate an AOO
3.4.x/OOo 3.x user profile [2]



I have solved both tasks inclusive the migration of user-installed 
extensions.


As the translation deadline has passed I have made no string changes.

Please provide feedback from your tests once a snapshot build or a 
buildbot build including these changes is available.


Best regards, Oliver.


In the last days I had a look at the user profile migration code and its
configuration. I figured out how it works in general.

Further investigation is needed to figure out, if and how the existing
service to 'migrate' installed extensions works. I am currently not
sure, if the automatic user profile migration should try to install
extensions from a former version. My current preference is not to
migrate extension from a former version.


I need support and help with the migration of the user profile:

(A) To figure out and test the user profile migration 'real-life' user
profiles or 'early-alpha-testers' would be welcome.
Thus, send my your AOO 3.4.x or OOo 3.x user profile in a compressed
form (.zip file or .tar.gz file or ...) or let me know, if you want to
try my builds.

(B) The first page of the FirstStartWizard is a general welcome
containing the following en-US strings.
String "This wizard will guide you through the license agreement, the
transfer of user data from %OLD_VERSION and the registration of
%PRODUCTNAME.", if a user profile for a migration is found, and string
"This wizard will guide you through the registration of %PRODUCTNAME."
otherwise.
Since at least OOo 3.2 no license agreement was shown --> no text for a
license agreement is needed on the welcome page.
Since AOO 3.4 we do not have a registration --> no text for a
registration has to be shown.
Thus, I am asking for new string proposals for the welcome page of the
FirstStartWizard.
I have attached screenshots of the currently deactivated FirstStartWizard.

[1] https://issues.apache.org/ooo/show_bug.cgi?id=122398
[2] https://issues.apache.org/ooo/show_bug.cgi?id=122397


Thanks in advance,
Oliver.


-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: Testing AOO 4.0 Upgrades

[Oliver-Rainer Wittmann]

Hi,

On 07.05.2013 14:17, Oliver-Rainer Wittmann wrote:

Hi,

On 07.05.2013 09:30, Shenfeng Liu wrote:

2013/5/7 Rob Weir 


On Mon, May 6, 2013 at 1:58 PM, janI  wrote:

On 6 May 2013 19:37, Rob Weir  wrote:


On Mon, May 6, 2013 at 1:25 PM, janI  wrote:

On 6 May 2013 18:27, Rob Weir  wrote:


What do we need to do to test AOO 4.0 -> AOO 4.1 upgrade scenario?



Do we already have documented procedures for the AOO 3.4.1 -> AOO 4.0
upgrade ?
(searching in wiki  for "4.0 upgrade" gives no result)

If not I would suggest we make the documentation and test plan for
the
3.4.1 -> 4.0 before thinking about the next upgrade.

One thing that really needs to be tested is a 3.4.1 danish (example)
installation, upgrade to a 4.0 english installation. At this point in

time

I foresee a 4.0 release with less languages than 3.4.1 (with language
respin). The tests should include fallback scenarios for users who

want

to

stay with their language version.



Two different things:

1) The upgrade notifications.  This is triggered by an XML file we put
on our website that the client checks, by default once a week.   For
example, here is one of the existing update notification files:




http://www.openoffice.org/projects/update38/ProductUpdateService/check.Update





ok my mistake, but I still think we should discuss this for 4.0 and not

4.1.




Let me be explicit.  We need to test AOO 4.0's ability to be correctly
process notifications about the existence of AOO 4.1.  And we need to
do that now, since after AOO 4.0 is installed on user's machines it is
too late to fix any client-side bugs in this area.

Some may remember, for example, a bug in AOO 3.4.0 where such
notifications were disabled by default.  And with 3.4.1 we had a bug
where in some cases clients crashed when checking for extension
updates.



The defect we had in AOO 3.4 and AOO 3.4.1 regarding the update
functionality - as far as I know - was the following:
- If the user had upgraded an OOo 3.3 installation with AOO 3.4 or AOO
3.4.1 the bundled extensions delivered with OOo 3.3 were deleted from
the installation, but the extension database still contains the
corresponding entries. During automatically triggered update check for
the application also an update check for the extensions is triggered.
Due to the inconsistent extension database the deleted bundled
extensions were tried to access. This causes an C++ exception which was
not caught and caused a crash. This is fixed for AOO 4.0.


So we do need to worry about AOO 4.1 now, at least to the extent AOO
4.0 needs support in its code to handle notifications about 4.1.



Rob,
   So my understanding for the purpose of this discussion thread is
that we
need to test the upgrade notice in AOO 4.0, and ensure it can work when
future releases (e.g. 4.1, 4.2...) available. Then I totally agree
that it
is very important and we need to add it to our test plan.
   While I want to confirm some technical details (and some of my
understanding below is from my reading of the URL you provided above):

1. Is the URL unique for each release? And this URL will work for all the
platforms and languages packages for this release?


The URL to check for application updates is unique for each release. At
least this is the case for the former releases and it will be for AOO 4.0.
It work for all platforms and languages.
The URL for AOO 4.0 will be
https://ooo-site.apache.org/projects/update/aoo40/check.Update
Have a look at main/instsetoo_native/util/openoffice.lst and search for
string "UPDATEURL"


2. Is the upgrade notice only for release upgrade purpose, but not
promotion of extensions or templates?


OpenOffice contains two update functions. One for the application update
and one for the extensions updates.
The update check for the extensions is automatically triggered (if
configured) at the same interval as the update check for the applications.
Each extension can provide its own URL for the update check, but there
is a fallback (URL currently not known to me).


It is 
http://updateexte.services.openoffice.org/ExtensionUpdateService/check.Update 
- found in main/scp2/source/ooo/common_brand.scp

But currently no update feeds are provided.

Best regards, Oliver.




3. For (A) and (B) below, I suppose they are not in AOO 4.0 scope, right?
4. For the testing perspective, can the URL be customized in AOO build
? If
yes, we may create a fake URL for development/testing purpose, without
impacting external users.


Yes, the URL can be changed - even when AOO is running.
Search for file "version.ini" (Windows) resp. "versionrc" (other
platforms) in your installation. It contains an entry starting with
string "UpdateURL=". You can simply change its value to another URL. You
can also use a "file://" URL to a file on your local file system.


Our wiki page [1] provides detailed information about the application
update functionality in OpenOffi

Re: Testing AOO 4.0 Upgrades

[Oliver-Rainer Wittmann]

Hi,

On 07.05.2013 09:30, Shenfeng Liu wrote:

2013/5/7 Rob Weir 


On Mon, May 6, 2013 at 1:58 PM, janI  wrote:

On 6 May 2013 19:37, Rob Weir  wrote:


On Mon, May 6, 2013 at 1:25 PM, janI  wrote:

On 6 May 2013 18:27, Rob Weir  wrote:


What do we need to do to test AOO 4.0 -> AOO 4.1 upgrade scenario?



Do we already have documented procedures for the AOO 3.4.1 -> AOO 4.0
upgrade ?
(searching in wiki  for "4.0 upgrade" gives no result)

If not I would suggest we make the documentation and test plan for the
3.4.1 -> 4.0 before thinking about the next upgrade.

One thing that really needs to be tested is a 3.4.1 danish (example)
installation, upgrade to a 4.0 english installation. At this point in

time

I foresee a 4.0 release with less languages than 3.4.1 (with language
respin). The tests should include fallback scenarios for users who

want

to

stay with their language version.



Two different things:

1) The upgrade notifications.  This is triggered by an XML file we put
on our website that the client checks, by default once a week.   For
example, here is one of the existing update notification files:




http://www.openoffice.org/projects/update38/ProductUpdateService/check.Update




ok my mistake, but I still think we should discuss this for 4.0 and not

4.1.




Let me be explicit.  We need to test AOO 4.0's ability to be correctly
process notifications about the existence of AOO 4.1.  And we need to
do that now, since after AOO 4.0 is installed on user's machines it is
too late to fix any client-side bugs in this area.

Some may remember, for example, a bug in AOO 3.4.0 where such
notifications were disabled by default.  And with 3.4.1 we had a bug
where in some cases clients crashed when checking for extension
updates.



The defect we had in AOO 3.4 and AOO 3.4.1 regarding the update 
functionality - as far as I know - was the following:
- If the user had upgraded an OOo 3.3 installation with AOO 3.4 or AOO 
3.4.1 the bundled extensions delivered with OOo 3.3 were deleted from 
the installation, but the extension database still contains the 
corresponding entries. During automatically triggered update check for 
the application also an update check for the extensions is triggered. 
Due to the inconsistent extension database the deleted bundled 
extensions were tried to access. This causes an C++ exception which was 
not caught and caused a crash. This is fixed for AOO 4.0.



So we do need to worry about AOO 4.1 now, at least to the extent AOO
4.0 needs support in its code to handle notifications about 4.1.



Rob,
   So my understanding for the purpose of this discussion thread is that we
need to test the upgrade notice in AOO 4.0, and ensure it can work when
future releases (e.g. 4.1, 4.2...) available. Then I totally agree that it
is very important and we need to add it to our test plan.
   While I want to confirm some technical details (and some of my
understanding below is from my reading of the URL you provided above):

1. Is the URL unique for each release? And this URL will work for all the
platforms and languages packages for this release?


The URL to check for application updates is unique for each release. At 
least this is the case for the former releases and it will be for AOO 4.0.

It work for all platforms and languages.
The URL for AOO 4.0 will be
https://ooo-site.apache.org/projects/update/aoo40/check.Update
Have a look at main/instsetoo_native/util/openoffice.lst and search for 
string "UPDATEURL"



2. Is the upgrade notice only for release upgrade purpose, but not
promotion of extensions or templates?


OpenOffice contains two update functions. One for the application update 
and one for the extensions updates.
The update check for the extensions is automatically triggered (if 
configured) at the same interval as the update check for the applications.
Each extension can provide its own URL for the update check, but there 
is a fallback (URL currently not known to me).



3. For (A) and (B) below, I suppose they are not in AOO 4.0 scope, right?
4. For the testing perspective, can the URL be customized in AOO build ? If
yes, we may create a fake URL for development/testing purpose, without
impacting external users.


Yes, the URL can be changed - even when AOO is running.
Search for file "version.ini" (Windows) resp. "versionrc" (other 
platforms) in your installation. It contains an entry starting with 
string "UpdateURL=". You can simply change its value to another URL. You 
can also use a "file://" URL to a file on your local file system.



Our wiki page [1] provides detailed information about the application 
update functionality in OpenOffice.




- Shenfeng (Simon)







There is a different base URL for each version, pointing to a file
like this that lists the available upgrades for that version.

Since the update checking code has changed, we should make sure we
have good testing on that, on all platforms.  There was also talk of
making that update check occur

Re: [sidebar] request for defect confirmation

[Oliver-Rainer Wittmann]

Hi,

On 07.05.2013 09:44, Oliver-Rainer Wittmann wrote:

Hi,

thanks for the feedback.

My own investigation on Ubuntu 11.10 32bit and 64bit reveals the following:
- the current snapshot builds show the defect
- the linux64 buildbot result (rev. 1479357) from yesterday (2013-05-06)
shows the defect
- my own build (rev. 1479493) on Ubuntu 11.10 32bit does _not_ show the
defect
- my own build (rev. 1479493) on Ubuntu 11.10 64bit does _not_ show the
defect



When I replace libstdc++.so.6 of the snapshot build installations resp. 
linux64 buildbot result installation with the one of my own build 
installation the defect does _not_ occur any more.



Best regards, Oliver.


Thus, I currently have no version which I can debug in order to find the
root cause and to fix the issue.
[The changes between rev. 1479357 and 1479493 are not fixing the problem
from my point of view.]

Can somebody support me here?
Somebody with AOO developer skills able to reproduce it in her/his Linux
environment?

Best regards, Oliver.

On 06.05.2013 21:47, Hagar Delest wrote:

Confirmed on:
AOO400m1(Build:9700)
2013-05-03 07:08:08 (Fri, 03 May 2013) - Linux x86_64
Ubuntu 13.04 (64bit)

Highlight color is displayed in Draw, Calc and Impress.

Hagar


Le 06/05/2013 14:17, Oliver-Rainer Wittmann a écrit :


Hi,

while investigating issue 122047 I figured out that the sidebar panels
which contains controls which are hidden/shown/enabled/disabled in
certain contexts are not reflecting the context dependency under Linux.
These are the Text property panel, the Paragraph property panel and
the Position and Size panel.
Example working under Windows, but not under Linux in my environments:
In the Text property panel the highlight color control should be
hidden in Calc, Draw and Impress. This is not the case under Linux -
at least in my environments.

Can somebody please confirm my observation?

Thanks in advance, Oliver.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [sidebar] request for defect confirmation

[Oliver-Rainer Wittmann]

Hi,

thanks for the feedback.

My own investigation on Ubuntu 11.10 32bit and 64bit reveals the following:
- the current snapshot builds show the defect
- the linux64 buildbot result (rev. 1479357) from yesterday (2013-05-06) 
shows the defect
- my own build (rev. 1479493) on Ubuntu 11.10 32bit does _not_ show the 
defect
- my own build (rev. 1479493) on Ubuntu 11.10 64bit does _not_ show the 
defect


Thus, I currently have no version which I can debug in order to find the 
root cause and to fix the issue.
[The changes between rev. 1479357 and 1479493 are not fixing the problem 
from my point of view.]


Can somebody support me here?
Somebody with AOO developer skills able to reproduce it in her/his Linux 
environment?


Best regards, Oliver.

On 06.05.2013 21:47, Hagar Delest wrote:

Confirmed on:
AOO400m1(Build:9700)
2013-05-03 07:08:08 (Fri, 03 May 2013) - Linux x86_64
Ubuntu 13.04 (64bit)

Highlight color is displayed in Draw, Calc and Impress.

Hagar


Le 06/05/2013 14:17, Oliver-Rainer Wittmann a écrit :


Hi,

while investigating issue 122047 I figured out that the sidebar panels
which contains controls which are hidden/shown/enabled/disabled in
certain contexts are not reflecting the context dependency under Linux.
These are the Text property panel, the Paragraph property panel and
the Position and Size panel.
Example working under Windows, but not under Linux in my environments:
In the Text property panel the highlight color control should be
hidden in Calc, Draw and Impress. This is not the case under Linux -
at least in my environments.

Can somebody please confirm my observation?

Thanks in advance, Oliver.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [sidebar] request for defect confirmation

[Oliver-Rainer Wittmann]

Hi,

On 06.05.2013 15:01, Oliver-Rainer Wittmann wrote:

Hi,

On 06.05.2013 14:17, Oliver-Rainer Wittmann wrote:

Hi,

while investigating issue 122047 I figured out that the sidebar panels
which contains controls which are hidden/shown/enabled/disabled in
certain contexts are not reflecting the context dependency under Linux.
These are the Text property panel, the Paragraph property panel and the
Position and Size panel.
Example working under Windows, but not under Linux in my environments:
In the Text property panel the highlight color control should be hidden
in Calc, Draw and Impress. This is not the case under Linux - at least
in my environments.


I had tested the recent snapshot builds.



I observed the same issue with the Linux 64bit build bot installation 
set under Ubuntu 11.10 64bit




Can somebody please confirm my observation?

Thanks in advance, Oliver.


-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [sidebar] request for defect confirmation

[Oliver-Rainer Wittmann]

Hi,

On 06.05.2013 14:17, Oliver-Rainer Wittmann wrote:

Hi,

while investigating issue 122047 I figured out that the sidebar panels
which contains controls which are hidden/shown/enabled/disabled in
certain contexts are not reflecting the context dependency under Linux.
These are the Text property panel, the Paragraph property panel and the
Position and Size panel.
Example working under Windows, but not under Linux in my environments:
In the Text property panel the highlight color control should be hidden
in Calc, Draw and Impress. This is not the case under Linux - at least
in my environments.


I had tested the recent snapshot builds.



Can somebody please confirm my observation?

Thanks in advance, Oliver.


-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

[sidebar] request for defect confirmation

[Oliver-Rainer Wittmann]

Hi,

while investigating issue 122047 I figured out that the sidebar panels 
which contains controls which are hidden/shown/enabled/disabled in 
certain contexts are not reflecting the context dependency under Linux.
These are the Text property panel, the Paragraph property panel and the 
Position and Size panel.

Example working under Windows, but not under Linux in my environments:
In the Text property panel the highlight color control should be hidden 
in Calc, Draw and Impress. This is not the case under Linux - at least 
in my environments.


Can somebody please confirm my observation?

Thanks in advance, Oliver.

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

[PUBLIC TALK] request for input for my talk "Apache OpenOffice - project status and release 4.0"

[Oliver-Rainer Wittmann]

Hi,

sorry for cross-posting - I want to reach all of you almost directly.
Please reply to d...@openoffice.apache.org.


I will give a talk on a German conference about Apache OpenOffice in mid 
April 2013 in Berlin. I had already mentioned this German conference in 
an earlier post [1]. The conference is about free office suite, mainly 
focused on Apache OpenOffice and LibreOffice, and the OpenDocument file 
format.
The title of my talk is "Apache OpenOffice - project status and release 
4.0".


In the first part I will present the continuation of the project at 
Apache and the actual project status. Some general remarks on the 
project structure and processes ("The Apache Way") will be included, I 
think. The main purpose of this part is to demonstrate how well 
OpenOffice evolves at Apache since the change the project had suffered 
in mid 2011. This will strengthen the confidence/trust in the project.


The second part is about our planned 4.0 release. The intention of this 
part is to show how active the development of the product and the 
project is by talking about the changes and improvements we had made/are 
making for our planned 4.0 release.



Now my _big_ request to you _all_.
I am only one person and I have more or less a developer view on the 
product and the project. E.g., I am not active on all our mailing lists. 
On certain areas I have no deep insight.
Thus, please provide me with information about the stuff that is going 
on in your area of interest.

What are the key milestones which you had achieved for the project?
What are your contributions for our coming 4.0 release?
[If wanted I can name the corresponding contributor(s) in the 
presentation document.]
The talk's length is 45 min. (30 min talk, 15 min Q&A) - I am able to 
fill the presentation with the stuff I know, but I strongly believe that 
in this case certain important stuff and details about the 
product/project will missing.


I will collect all your input and I will fill a wiki page with the 
summarized information. My presentation document will of course be 
available for further usage. If the presentation document will not be 
created at the last minute, I will also provide drafts of it for review 
and feedback.


I am looking forward for your input.


[1] 
http://mail-archives.apache.org/mod_mbox/openoffice-dev/201302.mbox/%3C512C9ED2.70601%40googlemail.com%3E



Big Thanks in advance,
Oliver.

-
To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
For additional commands, e-mail: qa-h...@openoffice.apache.org

Re: [QA REPORT] Bug 121429, doubts about this bug

[Oliver-Rainer Wittmann]

Hi,

On 13.02.2013 18:11, Rob Weir wrote:

On Tue, Feb 12, 2013 at 11:01 PM, Diego Valle Rosado
 wrote:

Hello all,

I was cheking the bug 121429- Justified lost in .docx bullet text list, the
user commented that OpenOffice loses formatting when importing MS Office
  Open XML .docx bullet or numbered lists.
He also says that Oliver-Rainer Wittmann has fixed a similar bug  .doc
files in the Bug 103711.
The following was the analysis of Oliver-Rainer:

"The analysis of Microsoft Word behavior reveals that the left indent for these
paragraphs are set at the paragraph itself, while the first line indent is set
at the corresponding list level of the applied list style.
When specifying the new position and space properties for list levels - see
specification http://specs.openoffice.org/writer/numbering/NewListLevelAttrs.odt
- such a situation has been overseen.
The problem that in OOo Writer all indent attributes (left indent, first line
indent and right indent) are combined in one attribute item makes it somehow
hard to take the left indent from the paragraph attributes and the first line
indent from the list level properties.

For the WW8 import I will implement the following solution:
- In case that a paragraph has only given a left indent and is inside a list
whose corresponding list level provides a first line indent the first
line indent from the list level is directly applied to the paragraph."


The user says that he has added a file to reproduce the bug but it hasn't done.

what can I do?, I tell him to add the file to reproduce the bug, or
change the status  as duplicate because Oliver-Rainer has corrected a
similar bug.




I'm cc'ing the programmer, Oliver-Rainer, to see if he agrees that
this sounds like a duplicate.



May be it is a duplicate. But the description talks about .docx import. 
In this case that fix which I had made in the .doc import needs to be 
implemented also in the .docx import. But the example document is named 
"BulletFormat.doc". Thus, I am not sure, if it is a .docx or a .doc 
document.
I have requested in the issue that the submitter should attach the 
mentioned example document.


Best regards, Oliver.

P.S.: I am not subscribed to the qa mailing list. Thus, please put my on 
CC when you want me to get your reply.