Re: [PROPOSAL] Managing branches for future releases

+1 so we can also show to be ready to fix important bugs in time. this is also a statement to the community Regards Mechtilde Am 25.10.2017 um 01:00 schrieb Patricia Shanahan: > > > On 10/24/2017 2:34 PM, Kay Schenk wrote: >> >> On 10/24/2017 01:25 PM, Andrea Pescetti wrote: >>> I'm starting

Re: Issue for 4.1.4 and MacOS

Hi - I’ve been trying to get Mac builds going today. I am trying right now with trunk. I’m still stuck on configure and have an XCodeLegacy question out to Jim on another thread. checking which jpeg to use... internal checking which expat to use... internal checking which libxslt to use... exte

Re: Issue for 4.1.4 and MacOS

Even if you can't get a Mac build going in time to help with this bug, we obviously need more people building and testing on Mac. On 10/24/2017 4:01 PM, Peter kovacs wrote: I do own a Mac. But its me. ;) I hope that maybe with the actual guide I can build. So far I failed to install the old co

Re: Issue for 4.1.4 and MacOS

I do own a Mac. But its me. ;) I hope that maybe with the actual guide I can build. So far I failed to install the old code on it. If I can manage to build, I could dig into the problem. I have a long weekend upcoming. Hope I can allocate time. Am 24. Oktober 2017 17:36:16 MESZ schrieb Jim Jagi

Re: [PROPOSAL] Managing branches for future releases

On 10/24/2017 2:34 PM, Kay Schenk wrote: On 10/24/2017 01:25 PM, Andrea Pescetti wrote: I'm starting a short series of occasional posts to capture the current collective state of mind on the next release. I'll float them here for refinement or lazy consensus, and then we may want to reuse th

Re: [PROPOSAL] Managing branches for future releases

Kay Schenk wrote: Would it be more clear to just remove the AOO415 branch and only re-instate it if needed (hopefully not). No, it wouldn't. See https://bz.apache.org/ooo/show_bug.cgi?id=127552 - there is a series of changes that need to be done for the release number bump. It's better to hav

[Build] XCodeLegacy - Re: dmake and epm

Hi Jim, I’m hung up on what I should do with https://github.com/devernay/xcodelegacy What should I download before I run the scripts? Which form of the command should I use? BTW - this requirement is only mentioned in the build release script. Regards

Re: [PROPOSAL] Managing branches for future releases

On 10/24/2017 01:25 PM, Andrea Pescetti wrote: I'm starting a short series of occasional posts to capture the current collective state of mind on the next release. I'll float them here for refinement or lazy consensus, and then we may want to reuse this text in wiki or blog posts to avoid repe

[PROPOSAL] Managing branches for future releases

I'm starting a short series of occasional posts to capture the current collective state of mind on the next release. I'll float them here for refinement or lazy consensus, and then we may want to reuse this text in wiki or blog posts to avoid repeating the same concepts over and over. Let's st

Re: QA Improvements on 4.2.0

Hi - I agree and wrote the same on a different thread the other day. Regards, Dave > On Oct 24, 2017, at 3:28 AM, Pedro Lino wrote: > > Hi Raphael, all > >> I believe the 4.1.4 shows us, that we have to do a better job in QA. A >> minor release should never go to a rc5. I believe we all (and

Re: Issue for 4.1.4 and MacOS

Will also follow up on the Bugz report, but one change between 4.1.3 and 4.1.4 regarding macOS *builds* is that 4.1.4 uses '--with-alloc=system' but the 4.1.3 build does not. I will create a macOS build of AOO414 but adjust the configure script to not include that and see what effect that may have

Re: Issue for 4.1.4 and MacOS

On 10/24/2017 5:49 AM, Rory O'Farrell wrote: On Tue, 24 Oct 2017 05:35:34 -0700 Patricia Shanahan wrote: Since the issue appeared in 4.1.4, and involves document links, it might be related to my changes. I do not have a Mac, and do not have any Mac debug experience. How do people think we

Re: Issue for 4.1.4 and MacOS

On Tue, 24 Oct 2017 05:35:34 -0700 Patricia Shanahan wrote: > Since the issue appeared in 4.1.4, and involves document links, it might > be related to my changes. > > I do not have a Mac, and do not have any Mac debug experience. > > How do people think we should proceed with this? Is there a

Re: Issue for 4.1.4 and MacOS

Since the issue appeared in 4.1.4, and involves document links, it might be related to my changes. I do not have a Mac, and do not have any Mac debug experience. How do people think we should proceed with this? Is there a Mac developer who can work with me on it? On 10/24/2017 4:40 AM, Larry

Re: Issue for 4.1.4 and MacOS

On 2017-10-24, 4:19 AM FR web forum wrote: Please have a look on: https://bz.apache.org/ooo/show_bug.cgi?id=127568 I tested and confirm the problem. Posted my result on the bug report. -- _ Larry I. Gusaas Moose Jaw, Saskatchewan Canada Website: http://larry-

Re: QA Improvements on 4.2.0

Hi Raphael, all > I believe the 4.1.4 shows us, that we have to do a better job in QA. A > minor release should never go to a rc5. I believe we all (and I pointing > my finger to myself) underestimated the regression risk at the 4.1.4. +1 > So, to do a better job in the 4.2.0 I propose the f

Issue for 4.1.4 and MacOS

Please have a look on: https://bz.apache.org/ooo/show_bug.cgi?id=127568 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Tajik hunspell dictionary

Odil Soliev wrote: We are prepare a Tajik hunspell dictionary for OpenOffice. How can we add our dictionary to OpenOffice distribution? After you are done with the dictionary (.dic and .aff files), package them into an extension and upload it to http://extensions.openoffice.org/ You can us