Re: [VOTE] Release Apache OpenOffice 4.1.3 RC1

[Mechtilde]

+1

Am 05.10.2016 um 23:07 schrieb Patricia Shanahan:
> The Apache OpenOffice 4.1.3 source and binaries,
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain
> several bug fixes. See the draft release notes at
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes
> 
> 
> Please vote on releasing it as 4.1.3 by replying to this thread
> 
> [ ] +1 Approve, with description of any testing you have done
> [ ] 0 Abstain
> [ ] -1 Disapprove, with explanation.
> 
> In addition, if you are a PMC member please indicate "Binding" if you
> intend to cast a binding vote, which requires a build and test from source.
> 
> Please tag any discussion, rather than votes, with [DISCUSS][VOTE].
> 
> The vote will conclude no sooner than 10 p.m UTC on Saturday, October
> 8th, 2016.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

-- 
Mechtilde Stehmann
--
## Apache OpenOffice.org
## Freie Office Suite für Linux, MacOSX, Windows
## Debian
## Loook, calender-exchange-provider, libreoffice-canzeley-client
## PGP encryption welcome
## Key-ID 0x141AAD7F



signature.asc
Description: OpenPGP digital signature

[Discussion] Office Architecture

[Peter Kovacs]

Hello all,


I am trying to understand the Architecture of OO. And i have a bit 
difficults to this. Mainly because I am Data Driven programmer (I suck 
when i have to write a gui), and the approach taken seems a GUI driven one.


So from hat I understand is, that on the Low lever we have "Primitives". 
Those Primitives are not an abstract view of Code, but already Graphical 
representations. (I found references from UNO to AWT. So I assume this.)


From these Primitives OO tailors an Abstract Toolset, called Framework 
which then get implemented into the Application like Writer or Calc etc.


Is this fundamental Idea of the Architecture correct?


Thanks

Peter


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

Re: [E-devel] Apache OpenOffice 4.1.2 locks in Enlightenment 0.21.99.21605

[Jose R R]

Howdy, Carsten-

As I was testing my build of ApacheOO 4.1.3, Enlightenment
0.21.99.21628 lock occurred again

< https://pbs.twimg.com/media/CuDUW33VIAA9ChB.jpg:large >


On Tue, Aug 30, 2016 at 4:45 PM, Carsten Haitzler  wrote:
> On Tue, 30 Aug 2016 04:22:00 -0700 Jose R R  said:
>
>> Thanks for replying.
>>
>> On Sun, Aug 28, 2016 at 11:27 PM, Carsten Haitzler 
>> wrote:
>> > On Sat, 27 Aug 2016 03:42:52 -0700 Jose R R  said:
>> >
>> >> Niltze [Hello], all!
>> >>
>> >> I've noticed that Enlightenment 0.17.x.y and 0.21.x.y GUI environment
>> >> sometimes becomes locked upon mousing over icons in Apache OpenOffice
>> >> 4.1.2.
>> >>
>> >> Notwithstanding, when I built Enlightenment 0.19.x.y and 0.20.xy, the
>> >> locking issue disappeared and I thought it was resolved; but then issue
>> >> reappeared once more in Enlightenment 0.21.x.y. I have to CTRL + ALT and
>> >> press F1, F2, etc. to get another shell, login and restart XDM.
>> >>
>> >> Any feedback would be greatly appreciated.
>> >
>> > is e stuck - has it crashed? do you get a crashdump?
>> E21 must be 'stuck' -- as I can't locate a 'crashdump'.
>>
>> Please see pic at:
>> <
>> https://metztli.it/blog/media/blogs/ixiptli/quick-uploads/p125/e21_apacheoo_issue.png?mtime=1472553272
>> >
>> >
>> > https://www.enlightenment.org/docs-efl-debug
>> I will try this as time avails. Thank you.
>> >
>> > you can also find if it isnt crashing by forcing a segv and seeing where
>> > the bt says it was stuck:
>> >
>> > killall -SEGV enlightenment
>> I have executed above directive and Recovery option seems useful -- as
>> I don't have to restart XDM, thus potentially preserving existing
>> sessions and/or data/work; again, please snapshot above and if
>> interested for context, post entry:
>> <
>> https://metztli.it/blog/index.php/ixiptli/eterm-and-enlightenment-window-manager
>> >
>
> so when you sent a SEGV to enlightenment... after that did you have
> ~/.e-crashdump.txt ? because you now FORCED it to crash, thus a crashdump
> should be produced. this may not work if yama ptrace is enabled.
>

e-crashdump_10-05-2016.txt attached below with latest crash at the end of file.

> sudo sysctl -w kernel.yama.ptrace_scope=0
>
>
> will turn that off. you need gdb installed too. also when compiling e and efl
> you need your CFFLAGS to contain "-g" to enable gdb debug symbols of course.
>
> export CFLAGS="-g -O2 -march=native -fvisibility=hidden -ffast-math"
>
> for example before you compile.
>
> remember - e APPENDS to the crashdump file every crash, so the most recent
> crash is the last bt set - grep for "pause" to find the crash points. :)
>
> so crashdump file after this? that'll tell use what's up. hopefully. or give 
> us
> another thing to follow.
>
> p.s.
>
> btw - why eterm? eterm is fine and all but its an old old old school terminal
> still using xlib directly etc. terminology is the modern terminal that uses 
> efl
> et. (runs even on OSX too) that has real bells and whistles (videos in the bg,
> inline image display, tabs AND splits etc.)? and it does PROPER transparency -
> no "esetroot" with fake "lets copy parts of the background pixmap into app
> window to make it look transparent but only with a wallpaper".

Apropos, I am also using Terminology ... with non-critical OS tasks:
Once upon a time, I had 5 concurrent Terminology tabs where one was
doing a Debian upgrade, the other 4 tabs I was doing some other tasks.
I switched tab to check on the OS upgrade status - and glimpsed a GUI
dialog prompting for something and then it disappeared into the
blackness of Terminology background. I had to CTRL + C to snap out of
the unintelligible prompt and ended up interrupting libc6 upgrade. I
had to reinstall OS ;-)

>
>> >
[...
]> --
> - Codito, ergo sum - "I code, therefore I am" --
> The Rasterman (Carsten Haitzler)ras...@rasterman.com
>

Anyhow, I just want Apache OpenOffice to be viable under
Enlightenment. Thank you in advance for your insight, Carsten.


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

Thread 5 (Thread 0x7fc64a2f1700 (LWP 3010)):
#0  0x7fc65808b577 in futex_abstimed_wait_cancelable (private=0, 
abstime=0x0, expected=0, futex_word=0x163d028) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
__ret = -512
oldtype = 0
err = 
#1  do_futex_wait (sem=sem@entry=0x163d028, abstime=0x0) at sem_waitcommon.c:111
No locals.
#2  0x7fc65808b624 in __new_sem_wait_slow (sem=0x163d028, abstime=0x0) at 
sem_waitcommon.c:181
_buffer = {__routine = 0x7fc65808b530 

Re: {Dicuss] [Vote]

[Patricia Shanahan]

On 10/5/2016 5:51 PM, Keith N. McKenna wrote:

Ariel Constenla-Haile wrote:

On Wed, Oct 05, 2016 at 07:17:27PM -0400, Keith N. McKenna wrote:

Patricia Shanahan wrote:

I believe, based on my tracking and testing, that the release blockers
are all fixed. I was hoping the people working on the bugs, especially
those who requested release_blocker, will update them ASAP.


I have no doubt that they have been fixed, but they need to be updated
as we link to a query for them from the Release Notes and what message
does it give to the world if the Release Notes show Release Blockers as
still open?


Most of these bugs don't make any sense in the release notes, they are
too aoo-build specific.


Regards


Ariel;

In all the builds that I have been involved in with AOO we have included
a link to a Bugzilla query for all bugs fixed by that release.My concern
was 2 fold. One that it would give a wrong impression to anyone that
followed the link and the second was to try to keep Bugzilla up to date.

If it is possible we should construct a query that excludes anything in
Product = Build Tools for the Release Notes.


I think calling out the important stuff directly in the release notes 
but providing a Bugzilla link that shows everything, including tools, is 
a reasonable compromise. However, I am very open to suggestions for 
improving the release notes.


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

Re: {Dicuss] [Vote]

[Keith N. McKenna]

Ariel Constenla-Haile wrote:
> On Wed, Oct 05, 2016 at 07:17:27PM -0400, Keith N. McKenna wrote:
>> Patricia Shanahan wrote:
>>> I believe, based on my tracking and testing, that the release blockers
>>> are all fixed. I was hoping the people working on the bugs, especially
>>> those who requested release_blocker, will update them ASAP.
>>>
>> I have no doubt that they have been fixed, but they need to be updated
>> as we link to a query for them from the Release Notes and what message
>> does it give to the world if the Release Notes show Release Blockers as
>> still open?
> 
> Most of these bugs don't make any sense in the release notes, they are
> too aoo-build specific.
> 
> 
> Regards
> 
Ariel;

In all the builds that I have been involved in with AOO we have included
a link to a Bugzilla query for all bugs fixed by that release.My concern
was 2 fold. One that it would give a wrong impression to anyone that
followed the link and the second was to try to keep Bugzilla up to date.

If it is possible we should construct a query that excludes anything in
Product = Build Tools for the Release Notes.

Regards
Keith



signature.asc
Description: OpenPGP digital signature

Re: {Dicuss] [Vote]

[Ariel Constenla-Haile]

On Wed, Oct 05, 2016 at 07:17:27PM -0400, Keith N. McKenna wrote:
> Patricia Shanahan wrote:
> > I believe, based on my tracking and testing, that the release blockers
> > are all fixed. I was hoping the people working on the bugs, especially
> > those who requested release_blocker, will update them ASAP.
> > 
> I have no doubt that they have been fixed, but they need to be updated
> as we link to a query for them from the Release Notes and what message
> does it give to the world if the Release Notes show Release Blockers as
> still open?

Most of these bugs don't make any sense in the release notes, they are
too aoo-build specific.


Regards
-- 
Ariel Constenla-Haile


signature.asc
Description: Digital signature

Re: {Dicuss] [Vote]

[Keith N. McKenna]

Patricia Shanahan wrote:
> I believe, based on my tracking and testing, that the release blockers
> are all fixed. I was hoping the people working on the bugs, especially
> those who requested release_blocker, will update them ASAP.
> 
I have no doubt that they have been fixed, but they need to be updated
as we link to a query for them from the Release Notes and what message
does it give to the world if the Release Notes show Release Blockers as
still open?

Regards
Keith

> On 10/5/2016 2:35 PM, Keith N. McKenna wrote:
>> Just a procedural Question. How can we be calling for a vote when there
>> are items in Bugzilla marked as release blockers that are not marked as
>> fixed?
>>
>> Regards
>> Keith
>>




signature.asc
Description: OpenPGP digital signature

Re: {Dicuss] [Vote]

[Patricia Shanahan]

They are now marked as fixed.

On 10/5/2016 3:28 PM, Patricia Shanahan wrote:

I believe, based on my tracking and testing, that the release blockers
are all fixed. I was hoping the people working on the bugs, especially
those who requested release_blocker, will update them ASAP.

On 10/5/2016 2:35 PM, Keith N. McKenna wrote:

Just a procedural Question. How can we be calling for a vote when there
are items in Bugzilla marked as release blockers that are not marked as
fixed?

Regards
Keith



-
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

Re: Testing 4.1.3 - source builds

[Patricia Shanahan]

On 10/5/2016 2:52 PM, Andrea Pescetti wrote:

On 04/10/2016 Mechtilde wrote:

Apache OpenOffice is a project with a wide user base, who only use the
binaries. So it is important to release well defined and tested binaries.


Yes, this is important. As we did for 4.1.2, I would leave PMC members
free to vote and specify what they have done. Nobody will go to jail for
not building from source and "only" testing the binaries that we are
going to make available for download by one million users per week.

We will not be in the situation where we should count votes and, if
needed (and it happened in the past) a release vote can be canceled by
the Release Manager if a blocker bug is found.

So it is more helpful for us to receive an honest +1 from someone who
specifies he only tested binaries than total silence from the same
person because she understood that you can be useful to the project only
if you build from source. It is clear that we will satisfy the mandatory
requirements anyway and with no need for counting votes. So the more
feedback we get, the better.


+1

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

Re: {Dicuss] [Vote]

[Patricia Shanahan]

I believe, based on my tracking and testing, that the release blockers 
are all fixed. I was hoping the people working on the bugs, especially 
those who requested release_blocker, will update them ASAP.


On 10/5/2016 2:35 PM, Keith N. McKenna wrote:

Just a procedural Question. How can we be calling for a vote when there
are items in Bugzilla marked as release blockers that are not marked as
fixed?

Regards
Keith



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

Re: [VOTE] Release Apache OpenOffice 4.1.3 RC1

[Matthias Seidel]

+1

Binary testing: Tested german (de) binary on Windows 8.1 (32bit), Ubuntu
16.04.1 (64bit) and Xubuntu 16.04.1 (32bit).


Am 05.10.2016 um 23:07 schrieb Patricia Shanahan:
> The Apache OpenOffice 4.1.3 source and binaries,
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain
> several bug fixes. See the draft release notes at
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes
>
> Please vote on releasing it as 4.1.3 by replying to this thread
>
> [ ] +1 Approve, with description of any testing you have done
> [ ] 0 Abstain
> [ ] -1 Disapprove, with explanation.
>
> In addition, if you are a PMC member please indicate "Binding" if you
> intend to cast a binding vote, which requires a build and test from
> source.
>
> Please tag any discussion, rather than votes, with [DISCUSS][VOTE].
>
> The vote will conclude no sooner than 10 p.m UTC on Saturday, October
> 8th, 2016.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

New AOO414 branch?

[Andrea Pescetti]

Can we open the AOO414 branch? Everything seems to show that 4.1.3 will 
be coming in a week or so and for sure there is no further code work to 
do on it. So I'd like to have an AOO414 branch where (once they are 
approved) we can start merging changes. OpenOffice 4.1.4 is not going to 
take another year, so better start early.

Regards,
  Andrea.

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

{Dicuss] [Vote]

[Keith N. McKenna]

Just a procedural Question. How can we be calling for a vote when there
are items in Bugzilla marked as release blockers that are not marked as
fixed?

Regards
Keith



signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Release Apache OpenOffice 4.1.3 RC1

[Patricia Shanahan]

+1 Binding

Source testing: Checked signature and hashes. Checked that the three 
source formats contain identical files. Built and tested en-US on 
Windows 8.1


Binary testing: Tested en-GB binary on Windows 7, Windows 8.1, Windows 
10, and Ubuntu 16.04. Also tested fr binary on Windows 8.1


On 10/5/2016 2:07 PM, Patricia Shanahan wrote:

The Apache OpenOffice 4.1.3 source and binaries,
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain
several bug fixes. See the draft release notes at
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes


Please vote on releasing it as 4.1.3 by replying to this thread

[ ] +1 Approve, with description of any testing you have done
[ ] 0 Abstain
[ ] -1 Disapprove, with explanation.

In addition, if you are a PMC member please indicate "Binding" if you
intend to cast a binding vote, which requires a build and test from source.

Please tag any discussion, rather than votes, with [DISCUSS][VOTE].

The vote will conclude no sooner than 10 p.m UTC on Saturday, October
8th, 2016.

-
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

[VOTE] Release Apache OpenOffice 4.1.3 RC1

[Patricia Shanahan]

The Apache OpenOffice 4.1.3 source and binaries, 
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain 
several bug fixes. See the draft release notes at 
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes


Please vote on releasing it as 4.1.3 by replying to this thread

[ ] +1 Approve, with description of any testing you have done
[ ] 0 Abstain
[ ] -1 Disapprove, with explanation.

In addition, if you are a PMC member please indicate "Binding" if you 
intend to cast a binding vote, which requires a build and test from source.


Please tag any discussion, rather than votes, with [DISCUSS][VOTE].

The vote will conclude no sooner than 10 p.m UTC on Saturday, October 
8th, 2016.


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

Question Regarding Limitations

[Abebe,Fitsum]

Hi,

We would like to leverage openoffice base but have a few questions:

-   Is there a limitation on how much data we can store in the 
database(imposed by the database itself)? How many rows can we store per table, 
etc...
-   Is there a built in API to import xml data to the database?

Thank you,

Fitsum Abebe
Sr. Software Engineer, PathNet
fitsum.ab...@cerner.com | 816-888-2569
[http://www.cerner.com/uploadedImages/email_logo.png]




CONFIDENTIALITY NOTICE This message and any included attachments are from 
Cerner Corporation and are intended only for the addressee. The information 
contained in this message is confidential and may constitute inside or 
non-public information under international, federal, or state securities laws. 
Unauthorized forwarding, printing, copying, distribution, or use of such 
information is strictly prohibited and may be unlawful. If you are not the 
addressee, please promptly delete this message and notify the sender of the 
delivery error by e-mail or you may call Cerner's corporate offices in Kansas 
City, Missouri, U.S.A at (+1) (816)221-1024.

Re: Post vote release actions

[Andrea Pescetti]

Patricia Shanahan wrote:

RM: Update
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3 to show
vote result etc.


The only important thing to update is that the release is available, 
since the page stays archived.



RM: Edit
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes
release notes to delete "DRAFT" note. - RM


Someone will also have to call for translations and coordinate translations.


RM: Use svn to move
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ to
https://dist.apache.org/repos/dist/release/openoffice/4.1.3/. See
https://lists.apache.org/thread.html/0b3416c973088efdf60056d2aae7f6cee0bd125be4370f3c0ff5324b@%3Cdev.openoffice.apache.org%3E
for Ariel's tip on how to do this without a full checkout.


SVN moves by URL. So you never need a full checkout for the mv (Ariel 
was addressing another issue, i.e., how to add a file to a directory 
without a full checkout). For moving, this command will work from any 
directory (one line):


$ svn mv https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1 
https://dist.apache.org/repos/dist/release/openoffice/4.1.3



Someone with SourceForge access: Upload to SourceForge using rsync.


This does need a full checkout (a full export to be precise). I have 
access, as several other PMC members; I can take care of this.



Modify OpenOffice web pages to reflect the new release.
Press release and announcement on apache.org home page.


...and for the post on https://blogs.apache.org/OOo/ I have access, but 
I thinks others do too, so I'd leave this to someone else - even though 
it may be a simple copy/paste from the announcement.


Regards,
  Andrea.

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

RE: Post vote release actions

[Gavin McDonald]

> -Original Message-
> From: Patricia Shanahan [mailto:p...@acm.org]
> Sent: Thursday, October 6, 2016 2:26 AM
> To: dev@openoffice.apache.org
> Subject: Post vote release actions
> 
> I plan to start the 4.1.3 vote today. This is a draft of the action list 
> assuming
> the vote passes. Please help by correcting, expanding, and adding anything
> missing.
> 
> RM: Update
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3 to
> show vote result etc.
> 
> RM: Edit
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Releas
> e+Notes
> release notes to delete "DRAFT" note. - RM
> 
> RM: Use svn to move
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ to
> https://dist.apache.org/repos/dist/release/openoffice/4.1.3/. See
> https://lists.apache.org/thread.html/0b3416c973088efdf60056d2aae7f6cee0
> bd125be4370f3c0ff5324b@%3Cdev.openoffice.apache.org%3E
> for Ariel's tip on how to do this without a full checkout.
> 
> Someone with SourceForge access: Upload to SourceForge using rsync.
> 
> Modify OpenOffice web pages to reflect the new release.
> 
> Press release and announcement on apache.org home page.

Press release should certainly involve Sally at press@ so please tip her off 
now.

OpenOffice also have a Blog :-

https://blogs.apache.org/OOo/ 

Someone should step up and volunteer to add a post there (any committer 
can get an account if they don’t already have one)

Gav...




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

Post vote release actions

[Patricia Shanahan]

I plan to start the 4.1.3 vote today. This is a draft of the action list 
assuming the vote passes. Please help by correcting, expanding, and 
adding anything missing.


RM: Update 
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3 to show 
vote result etc.


RM: Edit 
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes 
release notes to delete "DRAFT" note. - RM


RM: Use svn to move 
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ to 
https://dist.apache.org/repos/dist/release/openoffice/4.1.3/. See 
https://lists.apache.org/thread.html/0b3416c973088efdf60056d2aae7f6cee0bd125be4370f3c0ff5324b@%3Cdev.openoffice.apache.org%3E 
for Ariel's tip on how to do this without a full checkout.


Someone with SourceForge access: Upload to SourceForge using rsync.

Modify OpenOffice web pages to reflect the new release.

Press release and announcement on apache.org home page.

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

Re: Release 4.1.4 - Blocker candidates

[Marcus]

Am 10/05/2016 01:08 PM, schrieb Matthias Seidel:

Am 05.10.2016 um 12:59 schrieb Marcus:

Am 10/05/2016 12:24 PM, schrieb Matthias Seidel:

Sorry for highjacking this thread...


please don't. Just create a mail with new subject or at least change
the subject as I've done now.


OK, I will do so in the future.




I would like to promote some issues as release blocker for 4.1.4. The
issues are fixed in trunk and the code changes are minimal.

What would be the best way, as I see no possibility in my
bugzilla-account?


In the BZ issue look for "Flags". Click on "set flags" and choose the
"4.1.4_release_blocker" with its question mark. Then in any case write
a comment (why it should go into 4.1.4, if known range and risk of the
fix and others). This will send a mail to dev@, so that the Release
Manager can decide.


Well, I see no "Flags" in my account. Even not in the issue that I
reported myself...
So I am not supposed to set a flag...


OK, I've changed permissions for your account. Please check again.

Marcus


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

Re: Release 4.1.4 - Blocker candidates

[Matthias Seidel]

Am 05.10.2016 um 12:59 schrieb Marcus:
> Am 10/05/2016 12:24 PM, schrieb Matthias Seidel:
>> Sorry for highjacking this thread...
>
> please don't. Just create a mail with new subject or at least change
> the subject as I've done now.

OK, I will do so in the future.

>
>> I would like to promote some issues as release blocker for 4.1.4. The
>> issues are fixed in trunk and the code changes are minimal.
>>
>> What would be the best way, as I see no possibility in my
>> bugzilla-account?
>
> In the BZ issue look for "Flags". Click on "set flags" and choose the
> "4.1.4_release_blocker" with its question mark. Then in any case write
> a comment (why it should go into 4.1.4, if known range and risk of the
> fix and others). This will send a mail to dev@, so that the Release
> Manager can decide.

Well, I see no "Flags" in my account. Even not in the issue that I
reported myself...
So I am not supposed to set a flag...

regards

Matthias



smime.p7s
Description: S/MIME Cryptographic Signature

Release 4.1.4 - Blocker candidates

[Marcus]

Am 10/05/2016 12:24 PM, schrieb Matthias Seidel:

Sorry for highjacking this thread...


please don't. Just create a mail with new subject or at least change the 
subject as I've done now.



I would like to promote some issues as release blocker for 4.1.4. The
issues are fixed in trunk and the code changes are minimal.

What would be the best way, as I see no possibility in my bugzilla-account?


In the BZ issue look for "Flags". Click on "set flags" and choose the 
"4.1.4_release_blocker" with its question mark. Then in any case write a 
comment (why it should go into 4.1.4, if known range and risk of the fix 
and others). This will send a mail to dev@, so that the Release Manager 
can decide.


Marcus

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

Re: 4.1.3_release_blocker denied: [Issue 126622] Base 4.1.2 does not open Tables and Queries in Mac OSX

[Jim Jagielski]

I cannot recreate the bug on my setup, which is 10.11 with Java 7 and 8
installed.

> On Oct 5, 2016, at 5:40 AM, Patricia Shanahan  wrote:
> 
> On 10/5/2016 2:32 AM, Larry Gusaas wrote:
>> On 2016-10-05, 12:48 AM Andrea Pescetti wrote:
>> 
>>> Larry Gusaas wrote:
 Is this approved or not approved as a release blocker???
 I thought there was a fix for this.
 It is essential that this is fixed for Mac users.
>>> 
>>> As I understand it, the reason is lack of testing and, as explained by
>>> Ariel, system changes in the latest 2 versions of MacOS X that require
>>> build changes for this to work. But testing is easy: just download a
>>> 4.1.3-RC1 build from
>>> https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ and give
>>> your feedback in the issue. If this doesn't make it for 4.1.3, it is a
>>> clear candidate for 4.1.4 (which is surely not going to take one year!).
>>> 
>>> Regards,
>>>  Andrea.
>> 
>> Base works in 4.1.3-RC1. I worked in the build that Ariel posted on the
>> issue for this bug. Apparently it doesn't require build changes to work,
>> or have those changes been made. Or was Ariel referring to the bug that
>> means the legacy Java 6 is required for Java to work on AOO???
> 
> I tried to find out what was going on in the thread
> 
> https://lists.apache.org/thread.html/0e96354facb4683435be70f428f8381636b2becaa89b34ab7b5f3ef0@%3Cdev.openoffice.apache.org%3E
> 
> Subject: Status of "Base 4.1.2 does not open Tables and Queries in Mac OSX"
> 
> I could not get a clear consensus that it has been fixed in 4.1.3, so I could 
> not include it in the release notes as a fixed bug. There is still time to 
> change that.
> 
> 
> -
> 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

Re: 4.1.3_release_blocker denied: [Issue 126622] Base 4.1.2 does not open Tables and Queries in Mac OSX

[Larry Gusaas]

On 2016-10-05, 3:40 AM Patricia Shanahan wrote:

On 10/5/2016 2:32 AM, Larry Gusaas wrote:

On 2016-10-05, 12:48 AM Andrea Pescetti wrote:


Larry Gusaas wrote:

Is this approved or not approved as a release blocker???
I thought there was a fix for this.
It is essential that this is fixed for Mac users.


As I understand it, the reason is lack of testing and, as explained by
Ariel, system changes in the latest 2 versions of MacOS X that require
build changes for this to work. But testing is easy: just download a
4.1.3-RC1 build from
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ and give
your feedback in the issue. If this doesn't make it for 4.1.3, it is a
clear candidate for 4.1.4 (which is surely not going to take one year!).

Regards,
  Andrea.


Base works in 4.1.3-RC1. I worked in the build that Ariel posted on the
issue for this bug. Apparently it doesn't require build changes to work,
or have those changes been made. Or was Ariel referring to the bug that
means the legacy Java 6 is required for Java to work on AOO???


I tried to find out what was going on in the thread

https://lists.apache.org/thread.html/0e96354facb4683435be70f428f8381636b2becaa89b34ab7b5f3ef0@%3Cdev.openoffice.apache.org%3E 



Subject: Status of "Base 4.1.2 does not open Tables and Queries in Mac OSX"

I could not get a clear consensus that it has been fixed in 4.1.3, so I could not include it 
in the release notes as a fixed bug. There is still time to change that.


The inability to build on newer versions of OS X refer to fixing the bug that requires the 
legacy version of Java 6 be installed before any version of Java can be found by AOO. I 
currently have Java 1.8.0 installed and the legacy Java 1.6.0. AOO is using the 1.8 version but 
would not be able to use it if 1.6 was not also installed.


Each major update of macOS (previously known as Mac OS X) removes the legacy Java and requires 
it to be reinstalled before AOO will find the newer Java.



--
_

Larry I. Gusaas
Moose Jaw, Saskatchewan Canada
Website: http://larry-gusaas.com
"An artist is never ahead of his time but most people are far behind theirs." - 
Edgard Varese



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

Re: Testing 4.1.3 - release notes

[Matthias Seidel]

Sorry for highjacking this thread...

I would like to promote some issues as release blocker for 4.1.4. The
issues are fixed in trunk and the code changes are minimal.

What would be the best way, as I see no possibility in my bugzilla-account?

regards

Matthias


Am 05.10.2016 um 00:23 schrieb Patricia Shanahan:
> Could people working on the bugzilla entries check the status and
> update as appropriate?
>
> Note that I did not include the Mac Tables and Queries issue,
> https://bz.apache.org/ooo/show_bug.cgi?id=126622, in the release notes
> because I did not see enough confirmation that it is fixed. I have now
> denied it 4.1.3 release blocker, but added a request for 4.1.4.
>
> On 10/4/2016 2:47 PM, Marcus wrote:
>> Am 10/04/2016 10:31 PM, schrieb Patricia Shanahan:
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes
>>>
>>>
>>
>> ah, thanks. I've updated some text (e.g., separated the sec issue into
>> an own paragraph) and updated the link for the BZ issue list as it still
>> points to 4.0.1.
>>
>> I'm a bit worried about the many issues that are not fixed, resolved,
>> closed [1].
>>
>> But besides this it's OK. So, we are also done here.
>>
>> [1]
>> https://bz.apache.org/ooo/buglist.cgi?f1=flagtypes.name=equals=Importance_format=advanced=4.1.3_release_blocker%2B
>>
>>
>>
>> Marcus
>>
>>
>>
>>> On 10/4/2016 1:29 PM, Marcus wrote:
 OK, binary and source code testing is on a good way.

 What about the release notes. Are these somewhere reachable/readable
 already?
>>
>> -
>> 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
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: 4.1.3_release_blocker denied: [Issue 126622] Base 4.1.2 does not open Tables and Queries in Mac OSX

[Patricia Shanahan]

On 10/5/2016 2:32 AM, Larry Gusaas wrote:

On 2016-10-05, 12:48 AM Andrea Pescetti wrote:


Larry Gusaas wrote:

Is this approved or not approved as a release blocker???
I thought there was a fix for this.
It is essential that this is fixed for Mac users.


As I understand it, the reason is lack of testing and, as explained by
Ariel, system changes in the latest 2 versions of MacOS X that require
build changes for this to work. But testing is easy: just download a
4.1.3-RC1 build from
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ and give
your feedback in the issue. If this doesn't make it for 4.1.3, it is a
clear candidate for 4.1.4 (which is surely not going to take one year!).

Regards,
  Andrea.


Base works in 4.1.3-RC1. I worked in the build that Ariel posted on the
issue for this bug. Apparently it doesn't require build changes to work,
or have those changes been made. Or was Ariel referring to the bug that
means the legacy Java 6 is required for Java to work on AOO???


I tried to find out what was going on in the thread

https://lists.apache.org/thread.html/0e96354facb4683435be70f428f8381636b2becaa89b34ab7b5f3ef0@%3Cdev.openoffice.apache.org%3E

Subject: Status of "Base 4.1.2 does not open Tables and Queries in Mac OSX"

I could not get a clear consensus that it has been fixed in 4.1.3, so I 
could not include it in the release notes as a fixed bug. There is still 
time to change that.



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

Re: 4.1.3_release_blocker denied: [Issue 126622] Base 4.1.2 does not open Tables and Queries in Mac OSX

[Larry Gusaas]

On 2016-10-05, 12:48 AM Andrea Pescetti wrote:


Larry Gusaas wrote:

Is this approved or not approved as a release blocker???
I thought there was a fix for this.
It is essential that this is fixed for Mac users.


As I understand it, the reason is lack of testing and, as explained by Ariel, system changes 
in the latest 2 versions of MacOS X that require build changes for this to work. But testing 
is easy: just download a 4.1.3-RC1 build from 
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ and give your feedback in the 
issue. If this doesn't make it for 4.1.3, it is a clear candidate for 4.1.4 (which is surely 
not going to take one year!).


Regards,
  Andrea.


Base works in 4.1.3-RC1. I worked in the build that Ariel posted on the issue for this bug. 
Apparently it doesn't require build changes to work, or have those changes been made. Or was 
Ariel referring to the bug that means the legacy Java 6 is required for Java to work on AOO???




--
_

Larry I. Gusaas
Moose Jaw, Saskatchewan Canada
Website: http://larry-gusaas.com
"An artist is never ahead of his time but most people are far behind theirs." - 
Edgard Varese



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

Re: 4.1.3_release_blocker denied: [Issue 126622] Base 4.1.2 does not open Tables and Queries in Mac OSX

[Andrea Pescetti]

Larry Gusaas wrote:

Is this approved or not approved as a release blocker???
I thought there was a fix for this.
It is essential that this is fixed for Mac users.


As I understand it, the reason is lack of testing and, as explained by 
Ariel, system changes in the latest 2 versions of MacOS X that require 
build changes for this to work. But testing is easy: just download a 
4.1.3-RC1 build from 
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ and give 
your feedback in the issue. If this doesn't make it for 4.1.3, it is a 
clear candidate for 4.1.4 (which is surely not going to take one year!).


Regards,
  Andrea.

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