Re: [VOTE] Release 4.1.2-RC3 as OpenOffice 4.1.2
On 23.10.2015 13:50, Andrea Pescetti wrote: > So please VOTE on releasing RC3 (as defined above) as OpenOffice 4.1.2: > [ ] +1 Approve > [ ] 0 Abstain > [ ] -1 Disapprove, with explanation > +1 Approve de-deb 32 bit Regards Michael signature.asc Description: OpenPGP digital signature
Re: [VOTE] Release 4.1.2-RC3 as OpenOffice 4.1.2
[x] 0 Abstain It is still not clear, whether the fact, that I cannot build the delivered source on Windows 7 is a problem in my build environment or a bug in the source. Kind regards Regina Andrea Pescetti schrieb: We have been in the Release Candidate stage for three weeks and it is now time to start a VOTE for releasing OpenOffice 4.1.2. Source and binary packages for RC3 are available at https://dist.apache.org/repos/dist/dev/openoffice/ and the reference revision is r1709696. Many people helped in making this available, but let me think Juergen and Herbert again for their assistance and guidance. I'm initially keeping the VOTE just a bit longer than the minimum 72 hours: please vote by Monday 26 October, 14:00 UTC. Extensions are surely possible if there is a need for them, but I hope that the very long testing phase we've gone through helps in shortening the final approval phase. So please VOTE on releasing RC3 (as defined above) as OpenOffice 4.1.2: [ ] +1 Approve [ ] 0 Abstain [ ] -1 Disapprove, with explanation Regards, Andrea. - 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: [VOTE] Release 4.1.2-RC3 as OpenOffice 4.1.2
+1 Approve Andrea Pescetti 於 2015年10月26日 08:06 寫道: > On 23/10/2015 Andrea Pescetti wrote: >> So please VOTE on releasing RC3 (as defined above) as OpenOffice 4.1.2: >> [ ] +1 Approve >> [ ] 0 Abstain >> [ ] -1 Disapprove, with explanation > > +1 Approve > > Verified signatures, checksums, licenses, built from scratch on Linux, > tested Italian localization, tested bugfixes and ordinary usage. No > blockers found. > > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > -- Best regards, imacat ^_*' PGP Key http://www.imacat.idv.tw/me/pgpkey.asc <> News: http://www.wov.idv.tw/ Tavern IMACAT's http://www.imacat.idv.tw/ Woman in FOSS in Taiwan http://www.wofoss.org/ OpenOffice http://www.openoffice.org/ EducOO/OOo4Kids Taiwan http://www.educoo.tw/ Greenfoot Taiwan http://greenfoot.westart.tw/ signature.asc Description: OpenPGP digital signature
Does GPL apply when building AOO under CygWin?
Hello, I am currently building AOO sources with CygWin under Windows XP x86 using this instruction: https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7 According to the link below I must distribute executables under the terms of GPL3+ if the Cygwin DLL is linked: https://cygwin.com/licensing.html Is it the case? Is the Cygwin DLL linked when building AOO? Is it legal to distribute the AOO executables under the Apache license when CygWin is used? Regards, Roman. P.S.: I also posted this question here: https://forum.openoffice.org/en/forum/viewtopic.php?f=6&t=79966
[DISCUSS] [VOTE] Release 4.1.2-RC3 as OpenOffice 4.1.2
On 26/10/15 09:31, Regina Henschel wrote: > [x] 0 Abstain > > It is still not clear, whether the fact, that I cannot build the > delivered source on Windows 7 is a problem in my build environment or a > bug in the source. Regina I don't know why it doesn't build on your machine but I successfully built the tagged AOO410 branch for the RC on Windows, Mac and Linuxc 32/64 bit. It was always a clean fresh build to the latest tagged sources. The src tar balls are gnerated on Mac as I did it always in the past. The included config scripts for Mac are a mistake and were probably in all src releases in the past as well (good catch Damjan) Well I built the src tarball only on Mac because of the lack of time to do it on the other platforms as well. But again it iis the same source I used to build the binaries. Juergen > > Kind regards > Regina > > Andrea Pescetti schrieb: >> We have been in the Release Candidate stage for three weeks and it is >> now time to start a VOTE for releasing OpenOffice 4.1.2. >> >> Source and binary packages for RC3 are available at >> https://dist.apache.org/repos/dist/dev/openoffice/ >> and the reference revision is r1709696. Many people helped in making >> this available, but let me think Juergen and Herbert again for their >> assistance and guidance. >> >> I'm initially keeping the VOTE just a bit longer than the minimum 72 >> hours: please vote by Monday 26 October, 14:00 UTC. Extensions are >> surely possible if there is a need for them, but I hope that the very >> long testing phase we've gone through helps in shortening the final >> approval phase. >> >> So please VOTE on releasing RC3 (as defined above) as OpenOffice 4.1.2: >> [ ] +1 Approve >> [ ] 0 Abstain >> [ ] -1 Disapprove, with explanation >> >> Regards, >>Andrea. >> >> - >> 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: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [VOTE] Release 4.1.2-RC3 as OpenOffice 4.1.2
On 23/10/15 13:50, Andrea Pescetti wrote: > We have been in the Release Candidate stage for three weeks and it is > now time to start a VOTE for releasing OpenOffice 4.1.2. > > Source and binary packages for RC3 are available at > https://dist.apache.org/repos/dist/dev/openoffice/ > and the reference revision is r1709696. Many people helped in making > this available, but let me think Juergen and Herbert again for their > assistance and guidance. > > I'm initially keeping the VOTE just a bit longer than the minimum 72 > hours: please vote by Monday 26 October, 14:00 UTC. Extensions are > surely possible if there is a need for them, but I hope that the very > long testing phase we've gone through helps in shortening the final > approval phase. > > So please VOTE on releasing RC3 (as defined above) as OpenOffice 4.1.2: > [ ] +1 Approve > [ ] 0 Abstain > [ ] -1 Disapprove, with explanation > +1 approve, I use it already on my Mac and I have't found anything critical so far. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Extra files in 4.1.2-RC3 source package
On 25/10/15 11:15, Andrea Pescetti wrote: > Damjan reported an interesting finding a few hours ago: the source > package of OpenOffice 4.1.2-RC3 contains two extra files (which are not > in SVN) in "main/": MacOSXX64Env.Set and MacOSXX64Env.Set.sh. > > I've done a quick check and: > - The issue already exists in the 4.1.0 and 4.1.1 releases, and likely > in previous releases too. > - The extra files are there due to a glitch in the script that packages > sources (sources are not 100% the same as an svn export: for example, we > don't want to carry revision control specific elements around, so the > packages sources do not contain .svnignore files, and soon); similarly, > there is an extra Makefile, which is generated by the same process. > - The extra files have zero practical relevance since the configure > process will ignore them (on a Mac, it will will silently overwrite > them; on other systems, it will create the equivalent files and use > those during the build). > > I recommend that we continue voting on 4.1.2-RC3, since anyway this is > not an issue to fix in SVN. It is what would be called a "clerical > error" to blame on scripts. > > In any cases: > 1) I will work on fixing our source packages. I'll keep you posted on this. > 2) This is a clear example that shows we need to store all auxiliary > scripts in SVN too. I've collected all of them for binary builds already > and I'll commit them to SVN soon. This will help immensely in, for > example, the buildbots setup. > > Binary packages are, of course, totally unaffected by this issue. > > We should all be grateful to Damjan for finding a glitch that escaped > our scrutiny in the latest two (but possibly many more...) releases. > the src tar balls can be built in instsetoo_native/util dmake aoo_srcrelease the Mac config scripts were filtered out in the past before we switched to 64 bit on MacOS. The ant file (solenv/bin/srcrelease.xml) is a bit lazy and should be fixed to filter the correct files on Mac and of course the correct files on Windows and Linux. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [VOTE] Release 4.1.2-RC3 as OpenOffice 4.1.2
So please VOTE on releasing RC3 (as defined above) as OpenOffice 4.1.2: [ X ] +1 Approve [ ] 0 Abstain [ ] -1 Disapprove, with explanation Regards, Andrea. - 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: [DISCUSS] [VOTE] Release 4.1.2-RC3 as OpenOffice 4.1.2
Hi Jürgen, Jürgen Schmidt schrieb: On 26/10/15 09:31, Regina Henschel wrote: [x] 0 Abstain It is still not clear, whether the fact, that I cannot build the delivered source on Windows 7 is a problem in my build environment or a bug in the source. Regina I don't know why it doesn't build on your machine but I successfully built the tagged AOO410 branch for the RC on Windows, Mac and Linuxc 32/64 bit. It was always a clean fresh build to the latest tagged sources. The src tar balls are gnerated on Mac as I did it always in the past. The included config scripts for Mac are a mistake and were probably in all src releases in the past as well (good catch Damjan) Well I built the src tarball only on Mac because of the lack of time to do it on the other platforms as well. But again it iis the same source I used to build the binaries. If it is not my build environment, then it is likely a problem on Windows, because building in Cygwin is a little bit special. Sadly no one found the time to try building a src tar ball on Windows. We are not releasing binaries but source, and as long as nobody does a successful build of a src tall ball on Windows, I cannot vote +1 in good conscience. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Does GPL apply when building AOO under CygWin?
Hi > On 26 Oct 15, at 04:47, Roman Kuksin wrote: > > Hello, > > I am currently building AOO sources with CygWin under Windows XP x86 using > this instruction: > https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7 > > According to the link below I must distribute executables under the terms of > GPL3+ if the Cygwin DLL is linked: > https://cygwin.com/licensing.html > > Is it the case? > Is the Cygwin DLL linked when building AOO? > Is it legal to distribute the AOO executables under the Apache license when > CygWin is used? I don't think that is the case. See Red Hat's statement on that Cygwin page: "As a special exception to GPLv3+, Red Hat grants you permission to link software whose sources are distributed under a license that satisfies the Open Source Definition with libcygwin.a, without libcygwin.a itself causing the resulting program to be covered by GPLv3+." OO is licensed using Apache SL2. I haven't checked very recently, but that likely satisfies the OSI open source definition. Historically, usage of Cygwin, which has been extensive, and long (I've been advocating it and helping people with it since 2001, at least, and that includes some OO work) has not caused license panic. Red Hat seems intent on ensuring that calm prevails and that people use it freely and regularly without having that heart stopping moment of regret that would turn them to something else. But, I could be wrong here. About everything. Cheers, Louis > Regards, > Roman. > > P.S.: > I also posted this question here: > https://forum.openoffice.org/en/forum/viewtopic.php?f=6&t=79966 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS] [VOTE] Release 4.1.2-RC3 as OpenOffice 4.1.2
Niltze, all! On Mon, Oct 26, 2015 at 4:17 AM, Regina Henschel wrote: > Hi Jürgen, > > Jürgen Schmidt schrieb: >> >> On 26/10/15 09:31, Regina Henschel wrote: >>> >>> [x] 0 Abstain >>> >>> It is still not clear, whether the fact, that I cannot build the >>> delivered source on Windows 7 is a problem in my build environment or a >>> bug in the source. >> >> >> Regina I don't know why it doesn't build on your machine but I >> successfully built the tagged AOO410 branch for the RC on Windows, Mac >> and Linuxc 32/64 bit. It was always a clean fresh build to the latest >> tagged sources. The src tar balls are gnerated on Mac as I did it always >> in the past. The included config scripts for Mac are a mistake and were >> probably in all src releases in the past as well (good catch Damjan) >> >> Well I built the src tarball only on Mac because of the lack of time to >> do it on the other platforms as well. But again it iis the same source I >> used to build the binaries. > > > If it is not my build environment, then it is likely a problem on Windows, > because building in Cygwin is a little bit special. Sadly no one found the > time to try building a src tar ball on Windows. We are not releasing > binaries but source, and as long as nobody does a successful build of a src > tall ball on Windows, I cannot vote +1 in good conscience. > > Kind regards > Regina > > > Earlier, under limited time, I was unsuccessful in building ApacheOO from source in this GNU/Linux Debian Unstable environment. I tried several Java versions, including Zulu from Azul Systems. On the other hand, simply because I was not able to build it in my environment, it does not imply that ApacheOO 4.1.2-RC3 is not ready to become OpenOffice 4.1.2. I installed it into Debian Unstable and it performs beautifully. https://pbs.twimg.com/media/CSPi_4XVEAEvCHg.png:large Thank you to whoever built the binary! [X] +1 Approve RC3 to become ApacheOO 4.1.2 -- 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! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS] [VOTE] Release 4.1.2-RC3 as OpenOffice 4.1.2
On 26/10/15 12:17, Regina Henschel wrote: > Hi Jürgen, > > Jürgen Schmidt schrieb: >> On 26/10/15 09:31, Regina Henschel wrote: >>> [x] 0 Abstain >>> >>> It is still not clear, whether the fact, that I cannot build the >>> delivered source on Windows 7 is a problem in my build environment or a >>> bug in the source. >> >> Regina I don't know why it doesn't build on your machine but I >> successfully built the tagged AOO410 branch for the RC on Windows, Mac >> and Linuxc 32/64 bit. It was always a clean fresh build to the latest >> tagged sources. The src tar balls are gnerated on Mac as I did it always >> in the past. The included config scripts for Mac are a mistake and were >> probably in all src releases in the past as well (good catch Damjan) >> >> Well I built the src tarball only on Mac because of the lack of time to >> do it on the other platforms as well. But again it iis the same source I >> used to build the binaries. > > If it is not my build environment, then it is likely a problem on > Windows, because building in Cygwin is a little bit special. Sadly no > one found the time to try building a src tar ball on Windows. We are not > releasing binaries but source, and as long as nobody does a successful > build of a src tall ball on Windows, I cannot vote +1 in good conscience. > Regina, I used the tar.gz tarball and started a Windows build, everything looks good so fr and it is still building. stlport for example is finished, I don#t remeber what exactly your problems were. Herbert mentioned that he remembered problems with the zip file and cygwin and permissions. Well I don't know and as mentioned I used the tar.gz because it was smaller. I will let you know when the build is finished. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: University student looking for experience in contributing to the Open Office project
As per the previous mail, I have downgraded to jdk 1.7.0_79. I ran the configure script again, after downloading the junit jar, and got the following output at the end * Apache OpenOffice 420 configuration. * * * Configuration part of Apache OpenOffice 420 build is finished. * * Note: Be aware that you might not be able to build Apache OpenOffice if * you ignore any warnings that were generated during this configuration * process. * * - Disabling gtk-quickstarter - not supported on Mac. Use --disable-systray * - JAVA_HOME was not explicitly informed with --with-jdk-home. the configure script * - attempted to find JAVA_HOME automatically, but apparently it failed * - in case JAVA_HOME is incorrectly set, some projects with not be built correctly * * * USAGE: * Source MacOSXX64Env.Set (in tcsh) or MacOSXX64Env.Set.sh (in sh) * in order to set up the build-environment variables. * I have set the JAVA_HOME environment variable correctly as per the following command: echo $JAVA_HOME /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home This is pointing to the correct jdk home. This is output of java -version: java version "1.7.0_79" Java(TM) SE Runtime Environment (build 1.7.0_79-b15) Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode) Why is the configure script not able to find my JAVA_HOME automatically and what can I do to make this warning go away? Thanks Jatin On 10/25/15, 9:28 PM, "Andrea Pescetti" wrote: >PATHANGI JANARDHANAN JATINSHRAVAN wrote: >> I downgraded to Ant 1.8.4 and still I get the same issue. It is greater than >> 1.7.0 >> and 1.8.4 is sufficiently old enough at this point that I would expect it to >> work > >I confirm I can build with ant 1.9 (1.9.3, to be precise) with no issues. > >> so is there something else that is the problem here? My JDK is 1.8.0_45. > >It looks like this may be the problem. This has recently been discussed >on this list. Can you try building with Java 7? > >Note: in any case, when you have build issues the best thing to do is to >find your config.log file and upload it to http://pastebin.com/ (or any >other service) with expiration date set at one month and send the link >here. This will allow people to look at all diagnostic messages. And >this is helpful when, like in this case, the error given by configure is >actually not very precise. > >Regards, > Andrea. > >- >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: Does GPL apply when building AOO under CygWin?
Cygwin is used only for building Windows binaries. The resulting binaries are native Windows and neither use nor distribute the Cygwin DLL. (The Visual Studio VC++ tool chain is run from within the CygWin shell, and that is what provides the completely-native Windows binary for Apache OpenOffice. If you use the same build process, that will be the case for your builds with respect to Cygwin.) If your built binaries incorporate essential dependencies on third-party libraries, you must respect the license requirements on those libraries, as well as the Apache License version 2.0 (and other licenses) on the Apache OpenOffice source code. - Dennis > -Original Message- > From: Roman Kuksin [mailto:roman.kuk...@atapy.com] > Sent: Monday, October 26, 2015 01:47 > To: dev@openoffice.apache.org > Subject: Does GPL apply when building AOO under CygWin? > > Hello, > > I am currently building AOO sources with CygWin under Windows XP x86 > using this instruction: > https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_b > y_step#Windows_7 > > According to the link below I must distribute executables under the > terms of GPL3+ if the Cygwin DLL is linked: > https://cygwin.com/licensing.html > > Is it the case? > Is the Cygwin DLL linked when building AOO? > Is it legal to distribute the AOO executables under the Apache license > when CygWin is used? > > Regards, > Roman. > > P.S.: > I also posted this question here: > https://forum.openoffice.org/en/forum/viewtopic.php?f=6&t=79966 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Extra files in 4.1.2-RC3 source package
Jürgen Schmidt wrote: On 25/10/15 11:15, Andrea Pescetti wrote: Damjan reported an interesting finding a few hours ago: the source package of OpenOffice 4.1.2-RC3 contains two extra files (which are not in SVN) in "main/": MacOSXX64Env.Set and MacOSXX64Env.Set.sh. the src tar balls can be built in instsetoo_native/util dmake aoo_srcrelease Thank you Juergen, I added your notes to https://bz.apache.org/ooo/show_bug.cgi?id=126605 Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[impress] undraw polygons
Hi all, can someone tell me how to undraw/remove a polypolygon from a canvas? I found "CompositeOp" of "CanvasGraphic" and thought I could just set it to clear ( setCompositeOp( cppcanvas::CanvasGraphic::CLEAR ); ) before drawing and then just redraw the same polypolygon. But it does not work. I just want to undraw a painted polypolygon in aoo-trunk/main/slideshow/source/engine/slide/userpaintoverlay.cxx. I also tried to draw some polpolygons with alpha set to different values but they all look the same. (All drawn with 100% alpha) drawing a polypolygon with alpha set to 50 (alpha did not work for me): pPolyPoly->setStrokeWidth(50); pPolyPoly->setRGBALineColor( ::cppcanvas::makeColor( 100, 10, 10, 10 ) ); pPolyPoly->draw(); - Der perfekte Zeitpunkt seinen Gasversorger zu wechseln: http://www.anpa.de/index.php?action=gasvergleich - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Pending release tasks
Am 10/26/2015 12:58 AM, schrieb Andrea Pescetti: After we have a successful vote (hopefully soon), we'll have to start working on the last steps to distribute a release. They are tracked on https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 but for a short summary: nice plan, haven't seen this before - but maybe I've just overlooked the link in previous mails. 1) Preparing Release Notes. I've already updated https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2+Release+Notes but it still needs work. I can take care of it. Do you mean some more translations or specific things in the English text? 2) Upload to mirrors. Does anyone know how to copy files to SF, and how long it takes? If it is a lengthy operation I'd rather start it soon. If anyone is available, please step forward. Juergen has done this in the past (IMHO). So, maybe he tell you at least if it was a slow task. 3) Preparing the website. It's better if our many JS files are updated by someone who is familiar with them, but it looks like this time we won't have structural changes, so a simple change 4.1.1 -> 4.1.2 may suffice, we won't need a lot of testing. Right, I've prepared already the main website locally. The localized websites will come next. I can do the production update in the evening hours (European time). 4) Preparing a short press release. Nothing really big, something like https://blogs.apache.org/OOo/entry/announcing_apache_openoffice_4_1 can be OK, or something more elaborate if we manage to put together a few quotes (after all, it has been a while since 4.1.1, so a new release is significant news). 5) Enabling update notifications for 4.1.1. This can come gradually. To keep the download peak and therefore the load in the first days a bit lower, IMHO it's better to enable them a bit splitted - e.g., the Windows builds 1 week after the release, everything else 2 weeks after the release. If you want a timeline, I think we can aim at Monday for tasks #1 and (pending successful conclusion of the ongoing vote) #2, which means that the release could be as soon as tasks #3 and #4 are done, so one of Tuesday/Wednesday/Thursday night European time. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Pending release tasks
Andrea Pescetti wrote: 1) Preparing Release Notes. I've already updated https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2+Release+Notes but it still needs work. I can take care of it. I'm now done with describing the main content of the release at the URL above. Edits by Keith or other native speakers or anyone else are clearly welcome. This is the version to be used for translations. I'll now send a note to the l10n list. 2) Upload to mirrors. Does anyone know how to copy files to SF, and how long it takes? If it is a lengthy operation I'd rather start it soon. If anyone is available, please step forward. This is our next step. Marcus, did you take care of this for 4.1.1? I have no idea how to do this, but it is important to start populating SourceForge, since I expect it may take 24-48 hours. RC3 is the version to be copied: declaring the vote successful is, in this respect, a technicality that I will take care of. Packages are at https://dist.apache.org/repos/dist/dev/openoffice/ (this is an svn URL, not only a web URL), but if it is handier to grab them from elsewhere I have copies on a few servers (all with verifiable checksums of course). Just ask in case. 3) Preparing the website. It's better if our many JS files are updated by someone who is familiar with them, but it looks like this time we won't have structural changes, so a simple change 4.1.1 -> 4.1.2 may suffice, we won't need a lot of testing. Now that I recall, Marcus wrote that the best moment is in the evening (Europe time), right? Depending on step 2 above, this can be scheduled for any of the next evenings. 4) Preparing a short press release. Nothing really big, something like https://blogs.apache.org/OOo/entry/announcing_apache_openoffice_4_1 can be OK, or something more elaborate if we manage to put together a few quotes (after all, it has been a while since 4.1.1, so a new release is significant news). This is probably just a proof-read/enhanced copy of https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2+Release+Notes plus a quote by Dennis as Chair and by one of the new developers. 5) Enabling update notifications for 4.1.1. This can come gradually. For the record, the resource that needs to be updated is http://svn.apache.org/viewvc/openoffice/updates-site/trunk/ and it can be done on a per-language, per-version basis; so I don't expect to enable it immediately for all users. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Pending release tasks
On 26/10/2015 Marcus wrote: nice plan, haven't seen this before - but maybe I've just overlooked the link in previous mails. (Note: our messages crossed, so I had some wrong information in my previous mail). Yes, the page has been there for a while, with regular updates. Actually you got even credited since it is based on your earlier work on release planning pages! 1) Preparing Release Notes. I've already updated https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2+Release+Notes but it still needs work. I can take care of it. Do you mean some more translations or specific things in the English text? No, I meant that most of it was still generic text, which I have now replaced with 4.1.2-specific information. 2) Upload to mirrors. Does anyone know how to copy files to SF, and how long it takes? If it is a lengthy operation I'd rather start it soon. If anyone is available, please step forward. Juergen has done this in the past (IMHO). So, maybe he tell you at least if it was a slow task. OK. I thought you had done it. But I've now logged in on SourceForge and I see that several OpenOffice PMC members have access, including you, me, Juergen, Herbert, Gavin and others. So maybe I can simply start copying the files myself. 3) Preparing the website. ... Right, I've prepared already the main website locally. The localized websites will come next. I can do the production update in the evening hours (European time). Good, thanks! 5) Enabling update notifications for 4.1.1. This can come gradually. To keep the download peak and therefore the load in the first days a bit lower, IMHO it's better to enable them a bit splitted - e.g., the Windows builds 1 week after the release, everything else 2 weeks after the release. I agree. Priority should go to the English website, then localized websites, then updates (actually, there isn't a big difference between enabling updates for Windows and enabling them for all operating systems). Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Pending release tasks
Am 10/26/2015 10:47 PM, schrieb Andrea Pescetti: On 26/10/2015 Marcus wrote: nice plan, haven't seen this before - but maybe I've just overlooked the link in previous mails. (Note: our messages crossed, so I had some wrong information in my previous mail). Yes, the page has been there for a while, with regular updates. Actually you got even credited since it is based on your earlier work on release planning pages! ah, nice to know :-) 1) Preparing Release Notes. I've already updated https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2+Release+Notes but it still needs work. I can take care of it. Do you mean some more translations or specific things in the English text? No, I meant that most of it was still generic text, which I have now replaced with 4.1.2-specific information. 2) Upload to mirrors. Does anyone know how to copy files to SF, and how long it takes? If it is a lengthy operation I'd rather start it soon. If anyone is available, please step forward. Juergen has done this in the past (IMHO). So, maybe he tell you at least if it was a slow task. OK. I thought you had done it. But I've now logged in on SourceForge and I see that several OpenOffice PMC members have access, including you, me, Juergen, Herbert, Gavin and others. So maybe I can simply start copying the files myself. Until now there are no real blockers and no veto vote. So, starting the upload now shouldn't be wrong. I remember that it's possible to set a staging bit at SourceForge for the new 4.1.2 directory. Then it is not yet visible for the world and nobody would see that is deleted again - if you see the need for uploading again or new files. 3) Preparing the website. ... Right, I've prepared already the main website locally. The localized websites will come next. I can do the production update in the evening hours (European time). Good, thanks! With regards to this I've updated the release schedule. 5) Enabling update notifications for 4.1.1. This can come gradually. To keep the download peak and therefore the load in the first days a bit lower, IMHO it's better to enable them a bit splitted - e.g., the Windows builds 1 week after the release, everything else 2 weeks after the release. I agree. Priority should go to the English website, then localized websites, then updates (actually, there isn't a big difference between enabling updates for Windows and enabling them for all operating systems). OK, then we have the chance to differenciate between the languages to stretch the notifications over 2 weeks. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: University student looking for experience in contributing to the Open Office project
On Mon, Oct 26, 2015 at 7:37 AM, #PATHANGI JANARDHANAN JATINSHRAVAN# < jatinshr...@e.ntu.edu.sg> wrote: > As per the previous mail, I have downgraded to jdk 1.7.0_79. I ran the > configure script again, after downloading the junit jar, and got the > following output at the end > > * Apache OpenOffice 420 configuration. > * > * > * Configuration part of Apache OpenOffice 420 build is finished. > * > * Note: Be aware that you might not be able to build Apache OpenOffice if > * you ignore any warnings that were generated during this configuration > * process. > * > * - Disabling gtk-quickstarter - not supported on Mac. Use > --disable-systray > * - JAVA_HOME was not explicitly informed with --with-jdk-home. the > configure script > * - attempted to find JAVA_HOME automatically, but apparently it failed > * - in case JAVA_HOME is incorrectly set, some projects with not be built > correctly > * > * > * USAGE: > * Source MacOSXX64Env.Set (in tcsh) or MacOSXX64Env.Set.sh (in sh) > * in order to set up the build-environment variables. > * > > I have set the JAVA_HOME environment variable correctly as per the > following command: > > > echo $JAVA_HOME > /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home > > > This is pointing to the correct jdk home. This is output of java -version: > > java version "1.7.0_79" > Java(TM) SE Runtime Environment (build 1.7.0_79-b15) > Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode) > > Why is the configure script not able to find my JAVA_HOME automatically > and what can I do to make this warning go away? > > Thanks > Jatin > Probably the quickest way to solve this problem is to do a configure again (delete the existing MacOSXX64Env. * files first), and add the the configuration option: --with-jdk-home=/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home I am not a Mac developer, but hopefully this will solve the problem for you. > > > > > > > On 10/25/15, 9:28 PM, "Andrea Pescetti" wrote: > > >PATHANGI JANARDHANAN JATINSHRAVAN wrote: > >> I downgraded to Ant 1.8.4 and still I get the same issue. It is greater > than 1.7.0 > >> and 1.8.4 is sufficiently old enough at this point that I would expect > it to work > > > >I confirm I can build with ant 1.9 (1.9.3, to be precise) with no issues. > > > >> so is there something else that is the problem here? My JDK is 1.8.0_45. > > > >It looks like this may be the problem. This has recently been discussed > >on this list. Can you try building with Java 7? > > > >Note: in any case, when you have build issues the best thing to do is to > >find your config.log file and upload it to http://pastebin.com/ (or any > >other service) with expiration date set at one month and send the link > >here. This will allow people to look at all diagnostic messages. And > >this is helpful when, like in this case, the error given by configure is > >actually not very precise. > > > >Regards, > > Andrea. > > > >- > >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 > -- -- MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu
Re: Pending release tasks
Marcus wrote: 2) Upload to mirrors. Does anyone know how to copy files to SF... Until now there are no real blockers and no veto vote. So, starting the upload now shouldn't be wrong. Yes, I started the upload just to test it. It worked. Upload to SF is extremely fast, and actually I was able to upload all the en-US binaries in a couple minutes, and to download the Windows executable successfully a few minutes later. Unfortunately, we have some slowness on the ASF side, even though it is much better than it used to be; but I think that tomorrow morning European time all files will be on SourceForge. I remember that it's possible to set a staging bit at SourceForge for the new 4.1.2 directory. Then it is not yet visible for the world and nobody would see that is deleted again - if you see the need for uploading again or new files. Found it, thanks! (it's in the file properties and I hadn't noticed it). The 4.1.2 folder now contain en-US only and is set to be "staged". If there are no big surprises and if propagation is still smooth as it was for the en-US test, the release is only 24-48 hours away. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Pending release tasks
Excellent! > -Original Message- > From: Andrea Pescetti [mailto:pesce...@apache.org] > Sent: Monday, October 26, 2015 16:15 > To: dev@openoffice.apache.org > Subject: Re: Pending release tasks > > Marcus wrote: > 2) Upload to mirrors. Does anyone know how to copy files to SF... > > Until now there are no real blockers and no veto vote. So, starting > the > > upload now shouldn't be wrong. > > Yes, I started the upload just to test it. It worked. Upload to SF is > extremely fast, and actually I was able to upload all the en-US binaries > in a couple minutes, and to download the Windows executable successfully > a few minutes later. Unfortunately, we have some slowness on the ASF > side, even though it is much better than it used to be; but I think that > tomorrow morning European time all files will be on SourceForge. > > > I remember that it's possible to set a staging bit at SourceForge for > > the new 4.1.2 directory. Then it is not yet visible for the world and > > nobody would see that is deleted again - if you see the need for > > uploading again or new files. > > Found it, thanks! (it's in the file properties and I hadn't noticed it). > The 4.1.2 folder now contain en-US only and is set to be "staged". If > there are no big surprises and if propagation is still smooth as it was > for the en-US test, the release is only 24-48 hours away. > > Regards, >Andrea. > > - > 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
[RESULT] [VOTE] Release 4.1.2-RC3 as OpenOffice 4.1.2
On 23/10/2015 Andrea Pescetti wrote: We have been in the Release Candidate stage for three weeks and it is now time to start a VOTE for releasing OpenOffice 4.1.2. ... I'm initially keeping the VOTE just a bit longer than the minimum 72 hours: please vote by Monday 26 October, 14:00 UTC. ... So please VOTE on releasing RC3 (as defined above) as OpenOffice 4.1.2: [ ] +1 Approve [ ] 0 Abstain [ ] -1 Disapprove, with explanation VOTE has concluded, even though of course more feedback is always welcome in case someone could not give feedback during these 3.5 days. The OpenOffice community and PMC voted in favor of releasing 4.1.2-RC3 (r1709696) as Apache OpenOffice 4.1.2, with 10 "+1 Approve" votes (7 from the PMC), 2 "0 Abstain" votes (2 from the PMC) and no "-1 Disapprove" votes. Tally follows. imacat +1 jsc +1 kschenk +1 marcus +1 mechtilde +1 mikeadvo+1 pescetti+1 damjan 0 regina 0 Rory O'Farrell +1 Jose R R +1 Olaf Felka +1 The release is still a few days away due to the needed preparations. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
