Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

Hi Raphael, I am not sure if you forgot to write something? ;-) Matthias Am 20.05.2017 um 20:52 schrieb Raphael Bircher: > Am .05.2017, 12:30 Uhr, schrieb Matthias Seidel > : > >> Hi Jim, >> >> That is alright with me... >> >> ...if we start working on a 4.2.0

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

Am .05.2017, 12:30 Uhr, schrieb Matthias Seidel : Hi Jim, That is alright with me... ...if we start working on a 4.2.0 branch as soon as possible! ;-) Regards, Matthias Am 17.05.2017 um 17:36 schrieb Jim Jagielski: My plan is to hold off on accepting this...

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

Hi Jim, That is alright with me... ...if we start working on a 4.2.0 branch as soon as possible! ;-) Regards, Matthias Am 17.05.2017 um 17:36 schrieb Jim Jagielski: > My plan is to hold off on accepting this... > >> On May 3, 2017, at 2:36 PM, Marcus wrote: >> >> Am

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

Just out of curiosity, I built the 4.1.4 branch locally with the updated graphics for Windows. First step was en-US and de. Later I will add pt and jp. As expected there were no building problems, installation went fine and functionality is normal. Regards, Matthias Am 03.05.2017 um 23:17

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

OK, let's keep this update small and simple. I can "patch" those 2 graphics easily myself... ;-) Matthias Am 03.05.2017 um 23:17 schrieb Keith N. McKenna: > On 5/3/2017 2:36 PM, Marcus wrote: >> Am 03.05.2017 um 11:54 schrieb Matthias Seidel: >>> An installer for Windows (and macOS) with an

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

On 5/3/2017 2:36 PM, Marcus wrote: > Am 03.05.2017 um 11:54 schrieb Matthias Seidel: >> An installer for Windows (and macOS) with an outdated ASF logo is >> "broken" (in my eyes) ;-) >> >> 80% of our downloads are for Windows, 15% for macOS. They should see the >> new logo! > > the logos are

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

Obviously nobody looks at the splash screen, since the wrong URL has been there for about 4 years now... ;-) (When the splash screen was redesigned, the same URL was put in it again) So I think now it is time for a change and to close this bug. The ASF logos are also visible during installation

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

Am 03.05.2017 um 13:45 schrieb Jim Jagielski: I can't add a Target Milestone of 4.1.4 for BZ issue: https://bz.apache.org/ooo/show_bug.cgi?id=127253 strange, it wasn't existing for the "Installation" product but for others. I've now added it. Please test if it works for you. Marcus

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

Am 03.05.2017 um 11:54 schrieb Matthias Seidel: An installer for Windows (and macOS) with an outdated ASF logo is "broken" (in my eyes) ;-) 80% of our downloads are for Windows, 15% for macOS. They should see the new logo! the logos are visible just at 2 places: - splash screen --> With the

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

I can't add a Target Milestone of 4.1.4 for BZ issue: https://bz.apache.org/ooo/show_bug.cgi?id=127253 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail:

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

An installer for Windows (and macOS) with an outdated ASF logo is "broken" (in my eyes) ;-) 80% of our downloads are for Windows, 15% for macOS. They should see the new logo! Apart from that, no code! Just some graphics... Matthias Am 03.05.2017 um 00:11 schrieb Marcus: > Am 02.05.2017 um

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

Am 02.05.2017 um 23:51 schrieb Matthias Seidel: Am 02.05.2017 um 13:42 schrieb Jim Jagielski: On Mar 22, 2017, at 8:43 AM, Matthias Seidel wrote: If we decide to get the new ASF logos for the installer, we should also update the setup icons for Windows/macOS and

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

Am 02.05.2017 um 13:42 schrieb Jim Jagielski: >> On Mar 22, 2017, at 8:43 AM, Matthias Seidel >> wrote: >> >> Hi Raphael, >> >> Thank you for your effort! >> Hopefully Ariel will still be able to assist, but it is really time for a >> 4.1.4 RC. >> >> May I suggest

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

Jim Jagielski wrote: On May 2, 2017, at 7:42 AM, Jim Jagielski wrote: https://bz.apache.org/ooo/show_bug.cgi?id=127341 (Update bundled dictionaries for AOO 4.1.4 release) +1 as well... r1784925 r1784961 r1785175 r1793216 Backported to 4.1.4... It seems the Bugzilla bot

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

Jim Jagielski wrote: FWIW, I've kicked off a CentOS5.11 x64 build on my VM. My CentOS 64 builds are online and confirmed to be working by others who use it for daily tasks (see archives of this list, or just ask if you need a link). Unless you see a reason for making alternate ones, I think

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

Am 02.05.2017 um 22:11 schrieb Jim Jagielski: > Since I'm not doing a Windows build, I assume we don't need to install > it and have it part of the SVN tag?? I am not so familiar with the procedure, but that sounds reasonable. So whoever does the Windows builds has to make sure to include

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

Since I'm not doing a Windows build, I assume we don't need to install it and have it part of the SVN tag?? > On May 2, 2017, at 3:35 PM, Matthias Seidel > wrote: > > Am 02.05.2017 um 21:17 schrieb Jim Jagielski: >>> On May 2, 2017, at 3:01 PM, Matthias Seidel

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

Am 02.05.2017 um 21:17 schrieb Jim Jagielski: >> On May 2, 2017, at 3:01 PM, Matthias Seidel >> wrote: >> >> Hi Jim, >> >> https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24 >> >> We only have to make sure, that we bundle the most recent msvcr100.dll >> (32bit) for

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

> On May 2, 2017, at 3:01 PM, Matthias Seidel > wrote: > > Hi Jim, > > https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24 > > We only have to make sure, that we bundle the most recent msvcr100.dll > (32bit) for the windows build. > (see:

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

Hi Jim, https://bz.apache.org/ooo/show_bug.cgi?id=127176#c24 We only have to make sure, that we bundle the most recent msvcr100.dll (32bit) for the windows build. (see: .../main/external/msvcp100/README_msvcX100.dll.txt) Regards, Matthias P.S.: I will come back later with a full list of

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

Went OK... Will now kick off a x32 build... These are test builds, since we still have 2 backports pending:: > On Mar 22, 2017, at 8:43 AM, Matthias Seidel > wrote: > > Hi Raphael, > > Thank you for your effort! > Hopefully Ariel will still be able to assist, but

Re: 4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

> On May 2, 2017, at 7:42 AM, Jim Jagielski wrote: > >> >> https://bz.apache.org/ooo/show_bug.cgi?id=127341 >> (Update bundled dictionaries for AOO 4.1.4 release) >> > > +1 as well... > > r1784925 r1784961 r1785175 r1793216 > Backported to 4.1.4...

Re: Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

FWIW, I've kicked off a CentOS5.11 x64 build on my VM. I've updated the wiki build page (https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step) with some updates, most due to CentOS5 is now EOL and some urls have changed. Plus, I needed to manually install File::Path

Centos5 builds (Was: Re: Release 4.1.3 (4.1.4))

I have 2 CentOS5 VMs setup, one 32bit the other 64. Is anyone else on task for doing 4.1.4 build for these platforms or should I give it a go? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional

4.1.4 blockers (Was: Re: Release 4.1.3 (4.1.4))

> On Mar 22, 2017, at 8:43 AM, Matthias Seidel > wrote: > > Hi Raphael, > > Thank you for your effort! > Hopefully Ariel will still be able to assist, but it is really time for a > 4.1.4 RC. > > May I suggest that these "release blocker" should also be merged: >

Re: Release 4.1.3 (4.1.4)

I've confirmed that except for the '-with-build-version' param, all configure options and params for 4.1.4 (and, fwiw, 4.1.3) are the same as was done for 4.1.2... I have gone ahead modified '-with-build-version', have committed the script[1], and will use it. 1.

Re: Release 4.1.3 (4.1.4)

Am 02.04.2017 um 19:25 schrieb Andrea Pescetti: > On 20/03/2017 Andrea Pescetti wrote: >> I think I can provide >> proper Linux-64 builds from the AOO414 branch matching the 4.1.3 >> specifications (this won't happen before end of March). > > I've built the current state of the AOO414 branch

Re: Release 4.1.3 (4.1.4)

On 20/03/2017 Andrea Pescetti wrote: I think I can provide proper Linux-64 builds from the AOO414 branch matching the 4.1.3 specifications (this won't happen before end of March). I've built the current state of the AOO414 branch (again, this is not a Release Candidate) for all languages for

Re: Release 4.1.3 (4.1.4)

Am 02.04.2017 um 14:52 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds >> >> "The builds linked on this page are intended to be used for *final >> testing* of release candidates by community volunteers." >> But

Re: Release 4.1.3 (4.1.4)

Matthias Seidel wrote: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds "The builds linked on this page are intended to be used for *final testing* of release candidates by community volunteers." But the "Buildbot output area" links to a page with snapshots for

Re: Release 4.1.3 (4.1.4)

Hi Andrea, Thanks for the clarification! I found this page: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds "The builds linked on this page are intended to be used for *final testing* of release candidates by community volunteers." But the "Buildbot output

Re: Release 4.1.3 (4.1.4)

On 27/03/2017 Jim Jagielski wrote: My AOO 4.1.4 builds are ready for upload. Thanks! I've addressed the "where to upload" question separately. Note: these are best defined as AOO414 (this is a name of a branch, not of a product) builds since we are still not close to RC stage for OpenOffice

Re: Release 4.1.3 (4.1.4)

On 30/03/2017 Matthias Seidel wrote: Unfortunately there is no location for RC described in our cWiki: https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release Definitely a point that should be added... This is one of the processes where OpenOffice simply behaves as a normal

Re: Release 4.1.3 (4.1.4)

Hi Jim, Unfortunately there is no location for RC described in our cWiki: https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release Definitely a point that should be added... Regards, Matthias P.S.: Did you also build 4.2.0? Am 30.03.2017 um 14:54 schrieb Jim Jagielski: >>

Re: Release 4.1.3 (4.1.4)

> On Mar 27, 2017, at 1:17 PM, Jim Jagielski wrote: > > My AOO 4.1.4 builds are ready for upload. > Just need a location to drop 'em off at :) - To unsubscribe, e-mail:

Re: Release 4.1.3 (4.1.4)

My AOO 4.1.4 builds are ready for upload. Configure settings were: LANGS="ast bg ca ca-XR ca-XV cs da de el en-GB en-US es eu fi fr gd gl he hi hu it ja kid km ko lt nb nl pl pt pt-BR ru sk sl sr sv ta th tr vi zh-CN zh-TW" ./configure \ --with-build-version="$(date +"%Y-%m-%d

Re: Release 4.1.3 (4.1.4)

Hi Andrea, Am 24.03.2017 um 01:05 schrieb Andrea Pescetti: > On 22/03/2017 Matthias Seidel wrote: >> Hopefully Ariel will still be able to assist, but it is really time for >> a 4.1.4 RC. > > I hope so too, so I would still wait for him as the (currently) > appointed Release Manager to have the

Re: Release 4.1.3 (4.1.4)

On 22/03/2017 Matthias Seidel wrote: Hopefully Ariel will still be able to assist, but it is really time for a 4.1.4 RC. I hope so too, so I would still wait for him as the (currently) appointed Release Manager to have the last word on blocker issues. This doesn't stop anybody from going on

Re: Release 4.1.3 (4.1.4)

Hi Jim, * That's ok, I think. Andrea told that he would have the builds not befor end march. And I'm happy if I have my Windows builds on Monday too. Regards, Raphael Am .03.2017, 12:59 Uhr, schrieb Jim Jagielski : I can have this complete and uploaded by this Monday if

Re: Release 4.1.3 (4.1.4)

I can have this complete and uploaded by this Monday if that's OK... I am currently traveling and my AOO build system isn't accessible from where I am. > On Mar 22, 2017, at 7:52 AM, Jim Jagielski wrote: > > >> On Mar 21, 2017, at 9:49 AM, Raphael Bircher

Re: Release 4.1.3 (4.1.4)

Hi Raphael, Thank you for your effort! Hopefully Ariel will still be able to assist, but it is really time for a 4.1.4 RC. May I suggest that these "release blocker" should also be merged: https://bz.apache.org/ooo/show_bug.cgi?id=127253 (Update the banners with the new ASF Logo)

Re: Release 4.1.3 (4.1.4)

Hi all Am .03.2017, 12:52 Uhr, schrieb Jim Jagielski : On Mar 21, 2017, at 9:49 AM, Raphael Bircher wrote: Is there someone who can do Mac OS X? As mentioned previously, I can. In fact, I have, but it was not a full-distclean rebuild, so

Re: Release 4.1.3 (4.1.4)

> On Mar 21, 2017, at 9:49 AM, Raphael Bircher wrote: > > > Is there someone who can do Mac OS X? > As mentioned previously, I can. In fact, I have, but it was not a full-distclean rebuild, so will do again, just to make sure. Once done, will upload. Suggested

Re: Release 4.1.3 (4.1.4)

Raphael Bircher wrote: Is there someone who can do Mac OS X? And Linux 32bit? Linux 32-bit is not substantially different from the 64-bit case (even if it needs to be done on a 32-bit virtual machine). I can probably setup a VM for Linux 32-bit too, further in April. That said, Linux

Re: Release 4.1.3 (4.1.4)

Hi all Am .03.2017, 23:42 Uhr, schrieb Andrea Pescetti : Raphael Bircher wrote: @Ariel please give a comment, if you are able to create the Release or not. If not, I'm willing to volunteer as release manager. More than a Release Manager we need builds. Can you put

Re: Release 4.1.3 (4.1.4)

Raphael Bircher wrote: @Ariel please give a comment, if you are able to create the Release or not. If not, I'm willing to volunteer as release manager. More than a Release Manager we need builds. Can you put builds online for people to test? Even though it is (deliberately) complex to do so,