Re: [BUGZILLA] proposal for new entry in field Target Milestone
Hi, On 05.03.2014 19:07, Kay Schenk wrote: On Wed, Mar 5, 2014 at 8:23 AM, Oliver-Rainer Wittmann < orwittm...@googlemail.com> wrote: Hi, On 05.03.2014 15:35, Rob Weir wrote: On Wed, Mar 5, 2014 at 8:38 AM, Oliver-Rainer Wittmann wrote: Hi, as we have created branch AOO410 for our coming AOO 4.1.0 release I would like to propose a new entry for Bugzilla field 'Target Milestone'. Something like 'AOO.next'. It shall be used for the solved issues which won't be part of the AOO 4.1.0 release, but be part of the next following one. Once we had agreed on the version number for this release this new entry shall be renamed accordingly. Would it make sense to have two, like: AOO.next.micro AOO.next.minor That would map to things targeted for 4.1.1 (work done in the branch) versus 4.2.0 (work done in the trunk). It might make sense, but I think in this case we can name 'AOO.next.micro' directly '4.1.1' (we also know, what the next micro release will be) and it should be introduced right after our 4.1.0 release, when a corresponding issue comes to life. BTW, is it possible to rename an existing entry of 'Target Milestone' as I had propose above? Just my 2 cents. Best regards, Oliver. We seem to already have some similar terms in Target Milestone: AOO Later next build milestone 1 milestone 2 Currently, only '4.1.0' is selectable. The above mentioned ones seems to be deactivated. I think the idea of AOO.next is useful but next after what? Would it be useful to have an additional field used in conjunction with AOO.next? Yes, the name can be confusing. Does somebody have a good suggestion? Best regards, Oliver. -Rob Any objections? Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: 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: [RELEASE][DISCUSS] How to download AOO 4.1.0 Beta?
On 3/5/14 10:46 PM, Marcus (OOo) wrote: > Am 03/04/2014 07:31 AM, schrieb Jürgen Schmidt: >> On 3/3/14 9:24 PM, Marcus (OOo) wrote: >>> Am 02/14/2014 09:53 PM, schrieb Marcus (OOo): As this is our first beta release at Apache, I would like to clarify some things before it's maybe too late to change the facts and to prepare webpages: 3. File names: Of course the file names of the install files have to show a difference compared to the general release files. Suggestion: Apache_OpenOffice_4.1.0_Beta_Win_x86_install.exe *If* there is a need to publish another round, it could be extended with a number like: Apache_OpenOffice_4.1.0_Beta2_Win_x86_install.exe >>> >>> OK, I've learned that this won't be possible and the names will be >>> slightly different - but only as long as they are not uploaded to >>> Sourceforge. Therefore I suggest to rename them to the synxtax that was >>> used before (see above). >>> >>> I've created already a little shell script to do the work but won't >>> attach here. >>> >>> @Juergen: Is this something for you? >> >> no and I am not in favor or changing the names. I would like to use the >> names as they came out of the build. >> >> Please point me to the scripts that build the name for the download. It >> should be easy to put the beta string in the correct position. > > You want to edit the download scripting but not doing a 1 minute file > renaming? Hm ;-) I said that I would like to use the bits that comes out of the build process directly without any further touching. > >> We have already said why the naming scheme is different and that it >> requires more time to analyze and tweak the build process for a proper >> naming. We hope that we can cleanup and improve this for the next >> release. > > I have not asked to change the names in the build system but what comes > out of it. I know that but every extra step in the release phase that is not necessary shoudl be avoided. Changing the download script should be trivial as well. Nobody can say if we really will work on this cleanup and time for it. That means tweak the existing process to the names the build produce and not introduce a further step. > >> But for now I would like to avoid any extra step and the change in the >> download script is one place. Otherwise I have to change several places >> where I automate some pre-release steps. > > So, it seems you or me have to change something in order to get working > download. > > OK, don't worry I'll take care of it. again, point us to the relevant scripts or better to the place where I can find instructions to do that for cases where you are not available. Juergen > > Marcus > > > - > 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: [BUGZILLA] proposal for new entry in field Target Milestone
Hi, On 05.03.2014 22:46, Marcus (OOo) wrote: Am 03/05/2014 05:23 PM, schrieb Oliver-Rainer Wittmann: Hi, On 05.03.2014 15:35, Rob Weir wrote: On Wed, Mar 5, 2014 at 8:38 AM, Oliver-Rainer Wittmann wrote: Hi, as we have created branch AOO410 for our coming AOO 4.1.0 release I would like to propose a new entry for Bugzilla field 'Target Milestone'. Something like 'AOO.next'. It shall be used for the solved issues which won't be part of the AOO 4.1.0 release, but be part of the next following one. Once we had agreed on the version number for this release this new entry shall be renamed accordingly. Would it make sense to have two, like: AOO.next.micro AOO.next.minor That would map to things targeted for 4.1.1 (work done in the branch) versus 4.2.0 (work done in the trunk). It might make sense, but I think in this case we can name 'AOO.next.micro' directly '4.1.1' (we also know, what the next micro release will be) and it should be introduced right after our 4.1.0 release, when a corresponding issue comes to life. +1 I also think that we can name the things directly. For issues that should be fixed/resolved in the mid-term future, we can use the already existing "AOO Later". strong -1 from my side for using 'AOO Later'. my arguments are: - There are already more than 1800 issue having this 'Target Milestone'. - 'AOO Later' sounds like 'never' - just my experience from former days when we had 'OOo Later' as 'Target Milestone'. Best regards, Oliver. And if there is no idea how and when to fix it, then simply don#t set any target version. Marcus BTW, is it possible to rename an existing entry of 'Target Milestone' as I had propose above? Just my 2 cents. Best regards, Oliver. -Rob Any objections? Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: 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
Iterator debugging
With the transition from stlport to system STL we lost some (most?) debugging support for STL on Windows. The MSVC STL offers debugging support but that is not activated in our builds. There is, for example the _HAS_ITERATOR_DEBUGGING environment variable that is responsible for activating iterator debugging. However, that only works when doing a "retail build" (compiler message is "warning CRT1005: Iterator debugging not supported in retail builds.") Does anybody know how to turn off retail builds? Building a non-pro version of OpenOffice is apparently not enough. Additional ideas for debugging system STL are also welcome. Regards, Andre - 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.0 Beta (RC)
Hi all, this is a call for vote on releasing the available release candidate (RC) as Apache OpenOffice 4.1.0 Beta. The Beta release is intended to reach more early adopters and to receive more valuable feedback to improve potentially critical areas for the final release. Apache OpenOffice 4.1 is a minor update with many bugfixes and at least 2 major improvements. It's the first version where we have the iAccessibility2 support integrated and available. A very huge step forward to reach and better support disabled users especially on Windows. The second improvement is the switch to 64 bit on MacOS. A long and overdue "must do" shift forward to support newer APIs (replace deprecated APIs) and platforms on MacOS. And we can provide again more complete UI translations and have now support for 37 languages. New languages for this release compared to 4.0.1 are Bulgarian, Danish, Hindi, Norwegian Bokmal and Thai. Apache OpenOffice 4.1 will be a further key milestone to continue the success of OpenOffice. An overview of release issues can be found under: http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_Beta_fixes.html The release candidate artifacts (1) (source release, as well as binary releases for 37 languages) and further information how to verify and review Apache OpenOffice 4.1.0 Beta can be found on the following wiki page: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds The RC is based on the release branch AOO410, revision 1573601! And a fresh and clean RAT scan output of this revision can be found under http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_RAT_Scan.html Please vote on releasing this package as Apache OpenOffice 4.1.0 Beta The vote starts now and will be open until: Sunday evening, 9 March: 2014-03-09 11:00pm UTC. But we invite all people to vote (non binding) on this RC. We would like to provide a release that is supported by the majority of our project members. [ ] +1 Release this package as Apache OpenOffice 4.1.0 Beta [ ] 0 Don't care [ ] -1 Do not release this package because... (1) the upload for the Linux 32 bit artifacts is still ongoing, but 64 bit is already available. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Close, but not quite 100 million...
Hi, On 05.03.2014 20:47, Rob Weir wrote: If you look at the SourceForge page you'll see that shows 99.7 million downloads: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline?dates=2011-11-29+to+2014-03-18 But that number includes the downloads of Language Packs. The more conservative number that we report on the blog has always been the number of full product downloads. So if someone downloads AOO and also downloaded a Language Pack it would be counted as only a single download. The number of full-product downloads is around 95 million. So we still have a little more to go before we pop the champagne. Maybe around ApacheCon next month we'll hit 1 million. Sooner if we count beta downloads, but I'd recommend against counting beta downloads. Beta downloads should not be counted for the overall download statistic. But, the number of Beta downloads will be quite interesting in order to assess the general interest in such Beta release is. Best regards, Oliver. In any case, it is not too early to start thinking about what we want to do to publicize the 100 million number, when we do hit it. We'll do a blog post, of course. It would be awesome if we could design a special "100,000,000 downloads" logo that we could use on the website. Also, some better looking infographics would be nice. You can see what I typically produce, rather bland charts more suitable for a scientific report: https://blogs.apache.org/OOo/entry/75_million_downloads_of_apache I'm sure someone with more design sense could make something much better with the data. (and of course I can provide the updated data) Any other ideas? -Rob - 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
R: [VOTE]: Release Apache OpenOffice 4.1.0 Beta (RC)
+1 Messaggio originale Da: jogischm...@gmail.com Data: 6-mar-2014 9.55 A: "dev", , Ogg: [VOTE]: Release Apache OpenOffice 4.1.0 Beta (RC) Hi all, this is a call for vote on releasing the available release candidate (RC) as Apache OpenOffice 4.1.0 Beta. The Beta release is intended to reach more early adopters and to receive more valuable feedback to improve potentially critical areas for the final release. Apache OpenOffice 4.1 is a minor update with many bugfixes and at least 2 major improvements. It's the first version where we have the iAccessibility2 support integrated and available. A very huge step forward to reach and better support disabled users especially on Windows. The second improvement is the switch to 64 bit on MacOS. A long and overdue "must do" shift forward to support newer APIs (replace deprecated APIs) and platforms on MacOS. And we can provide again more complete UI translations and have now support for 37 languages. New languages for this release compared to 4.0.1 are Bulgarian, Danish, Hindi, Norwegian Bokmal and Thai. Apache OpenOffice 4.1 will be a further key milestone to continue the success of OpenOffice. An overview of release issues can be found under: http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_Beta_fixes.html The release candidate artifacts (1) (source release, as well as binary releases for 37 languages) and further information how to verify and review Apache OpenOffice 4.1.0 Beta can be found on the following wiki page: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds The RC is based on the release branch AOO410, revision 1573601! And a fresh and clean RAT scan output of this revision can be found under http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_RAT_Scan.html Please vote on releasing this package as Apache OpenOffice 4.1.0 Beta The vote starts now and will be open until: Sunday evening, 9 March: 2014-03-09 11:00pm UTC. But we invite all people to vote (non binding) on this RC. We would like to provide a release that is supported by the majority of our project members. [ ] +1 Release this package as Apache OpenOffice 4.1.0 Beta [ ] 0 Don't care [ ] -1 Do not release this package because... (1) the upload for the Linux 32 bit artifacts is still ongoing, but 64 bit is already available. - To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org For additional commands, e-mail: l10n-h...@openoffice.apache.org
Re: Compiler warnings
On 05.03.2014 14:42, Andre Fischer wrote: Exception support does make object files larger and possibly a bit slower. The question is, is that significant? To put some actual data behind this: the exception handling tables in the libraries cost us about 20MB (on our current 64bit Linux build). Twenty megabytes are certainly significant, but as they are useful this is a cost we have to bear. Module sw nowadays has exception support for all its files. And not changing at least the files in sc/ for which there are warnings might lead to memory leaks when there are exceptions. So it is probably best to activate support for exceptions module wide. There are files that use an "EXCEPTION_OFF" define to generate different code depending on whether exception handling is enabled or not. I suggest to analyze them and their uses... Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[RELEASE]: msp install sets to upgrade AOO 4.0.1 to AOO 4.1
Hi, for the Beta it is not possible to provide msp installer for Windows to upgrade from an AOO 4.0.1 to 4.1. But for the final RC I am planning to provide msp installer as well. The msp can be applied on a finally released and installed AOO 4.0.1 only and I plan to split the vote for the final release. One is for the full install sets, lang packs, SKD and source release and one for the msp's. If we detect any problems with the msp's we can easy drop it for 4.1. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE][DISCUSS] How to download AOO 4.1.0 Beta?
On 3/6/14 9:20 AM, Jürgen Schmidt wrote: > On 3/5/14 10:46 PM, Marcus (OOo) wrote: >> Am 03/04/2014 07:31 AM, schrieb Jürgen Schmidt: >>> On 3/3/14 9:24 PM, Marcus (OOo) wrote: Am 02/14/2014 09:53 PM, schrieb Marcus (OOo): > As this is our first beta release at Apache, I would like to clarify > some things before it's maybe too late to change the facts and to > prepare webpages: > > 3. File names: > > Of course the file names of the install files have to show a difference > compared to the general release files. Suggestion: > > Apache_OpenOffice_4.1.0_Beta_Win_x86_install.exe > > *If* there is a need to publish another round, it could be extended > with > a number like: > > Apache_OpenOffice_4.1.0_Beta2_Win_x86_install.exe OK, I've learned that this won't be possible and the names will be slightly different - but only as long as they are not uploaded to Sourceforge. Therefore I suggest to rename them to the synxtax that was used before (see above). I've created already a little shell script to do the work but won't attach here. @Juergen: Is this something for you? >>> >>> no and I am not in favor or changing the names. I would like to use the >>> names as they came out of the build. >>> >>> Please point me to the scripts that build the name for the download. It >>> should be easy to put the beta string in the correct position. >> >> You want to edit the download scripting but not doing a 1 minute file >> renaming? Hm ;-) > > I said that I would like to use the bits that comes out of the build > process directly without any further touching. > > >> >>> We have already said why the naming scheme is different and that it >>> requires more time to analyze and tweak the build process for a proper >>> naming. We hope that we can cleanup and improve this for the next >>> release. >> >> I have not asked to change the names in the build system but what comes >> out of it. > > I know that but every extra step in the release phase that is not > necessary shoudl be avoided. Changing the download script should be > trivial as well. > > Nobody can say if we really will work on this cleanup and time for it. > That means tweak the existing process to the names the build produce and > not introduce a further step. > > >> >>> But for now I would like to avoid any extra step and the change in the >>> download script is one place. Otherwise I have to change several places >>> where I automate some pre-release steps. >> >> So, it seems you or me have to change something in order to get working >> download. >> >> OK, don't worry I'll take care of it. > > again, point us to the relevant scripts or better to the place where I > can find instructions to do that for cases where you are not available. an overview of the Beta files can found under http://people.apache.org/~jsc/test/4.1.0-beta_files.txt IT is not yet 100% complete because the Linux upload is still ongoing. I will update it asap Juergen > > Juergen > >> >> Marcus >> >> >> - >> 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: [BUGZILLA] proposal for new entry in field Target Milestone
On 3/6/14 9:20 AM, Oliver-Rainer Wittmann wrote: > Hi, > > On 05.03.2014 22:46, Marcus (OOo) wrote: >> Am 03/05/2014 05:23 PM, schrieb Oliver-Rainer Wittmann: >>> Hi, >>> >>> On 05.03.2014 15:35, Rob Weir wrote: On Wed, Mar 5, 2014 at 8:38 AM, Oliver-Rainer Wittmann wrote: > Hi, > > as we have created branch AOO410 for our coming AOO 4.1.0 release I > would > like to propose a new entry for Bugzilla field 'Target Milestone'. > Something > like 'AOO.next'. It shall be used for the solved issues which won't > be part > of the AOO 4.1.0 release, but be part of the next following one. Once > we had > agreed on the version number for this release this new entry shall be > renamed accordingly. > Would it make sense to have two, like: AOO.next.micro AOO.next.minor That would map to things targeted for 4.1.1 (work done in the branch) versus 4.2.0 (work done in the trunk). >>> >>> It might make sense, but I think in this case we can name >>> 'AOO.next.micro' directly '4.1.1' (we also know, what the next micro >>> release will be) and it should be introduced right after our 4.1.0 >>> release, when a corresponding issue comes to life. >> >> +1 >> >> I also think that we can name the things directly. >> >> For issues that should be fixed/resolved in the mid-term future, we can >> use the already existing "AOO Later". >> > > strong -1 from my side for using 'AOO Later'. > my arguments are: > - There are already more than 1800 issue having this 'Target Milestone'. > - 'AOO Later' sounds like 'never' - just my experience from former days > when we had 'OOo Later' as 'Target Milestone'. I agree "AOO Later" is not the best choice, "AOO next" sounds much more positive and if we agree on using it only for issues where somebody is committed to fix it, it becomes much more useful. Juergen > > Best regards, Oliver. > >> And if there is no idea how and when to fix it, then simply don#t set >> any target version. >> >> Marcus >> >> >> >>> BTW, is it possible to rename an existing entry of 'Target Milestone' as >>> I had propose above? >>> >>> Just my 2 cents. >>> >>> Best regards, Oliver. >>> -Rob > Any objections? > > > Best regards, Oliver. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >>> - >>> To unsubscribe, e-mail: 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 Apache OpenOffice 4.1.0 Beta (RC)
+1 2014-03-06 16:55 GMT+08:00 Jürgen Schmidt : > Hi all, > > this is a call for vote on releasing the available release candidate > (RC) as Apache OpenOffice 4.1.0 Beta. The Beta release is intended to > reach more early adopters and to receive more valuable feedback to > improve potentially critical areas for the final release. > > Apache OpenOffice 4.1 is a minor update with many bugfixes and at least > 2 major improvements. It's the first version where we have the > iAccessibility2 support integrated and available. A very huge step > forward to reach and better support disabled users especially on > Windows. The second improvement is the switch to 64 bit on MacOS. A long > and overdue "must do" shift forward to support newer APIs (replace > deprecated APIs) and platforms on MacOS. > And we can provide again more complete UI translations and have now > support for 37 languages. New languages for this release compared to > 4.0.1 are Bulgarian, Danish, Hindi, Norwegian Bokmal and Thai. > > Apache OpenOffice 4.1 will be a further key milestone to continue the > success of OpenOffice. > > An overview of release issues can be found under: > > > http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_Beta_fixes.html > > The release candidate artifacts (1) (source release, as well as binary > releases for 37 languages) and further information how to verify and > review Apache OpenOffice 4.1.0 Beta can be found on the following wiki > page: > > > https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds > > The RC is based on the release branch AOO410, revision 1573601! And a > fresh and clean RAT scan output of this revision can be found under > > > http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_RAT_Scan.html > > Please vote on releasing this package as Apache OpenOffice 4.1.0 Beta > > The vote starts now and will be open until: > >Sunday evening, 9 March: 2014-03-09 11:00pm UTC. > > But we invite all people to vote (non binding) on this RC. We would like > to provide a release that is supported by the majority of our project > members. > >[ ] +1 Release this package as Apache OpenOffice 4.1.0 Beta >[ ] 0 Don't care >[ ] -1 Do not release this package because... > > > > (1) the upload for the Linux 32 bit artifacts is still ongoing, but 64 > bit is already available. > > - > 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.0 Beta (RC)
+1 for release Sylvain DENIS Belgium Le 06/03/14 14:03, Shenfeng Liu a écrit : +1 2014-03-06 16:55 GMT+08:00 Jürgen Schmidt : Hi all, this is a call for vote on releasing the available release candidate (RC) as Apache OpenOffice 4.1.0 Beta. The Beta release is intended to reach more early adopters and to receive more valuable feedback to improve potentially critical areas for the final release. Apache OpenOffice 4.1 is a minor update with many bugfixes and at least 2 major improvements. It's the first version where we have the iAccessibility2 support integrated and available. A very huge step forward to reach and better support disabled users especially on Windows. The second improvement is the switch to 64 bit on MacOS. A long and overdue "must do" shift forward to support newer APIs (replace deprecated APIs) and platforms on MacOS. And we can provide again more complete UI translations and have now support for 37 languages. New languages for this release compared to 4.0.1 are Bulgarian, Danish, Hindi, Norwegian Bokmal and Thai. Apache OpenOffice 4.1 will be a further key milestone to continue the success of OpenOffice. An overview of release issues can be found under: http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_Beta_fixes.html The release candidate artifacts (1) (source release, as well as binary releases for 37 languages) and further information how to verify and review Apache OpenOffice 4.1.0 Beta can be found on the following wiki page: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds The RC is based on the release branch AOO410, revision 1573601! And a fresh and clean RAT scan output of this revision can be found under http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_RAT_Scan.html Please vote on releasing this package as Apache OpenOffice 4.1.0 Beta The vote starts now and will be open until: Sunday evening, 9 March: 2014-03-09 11:00pm UTC. But we invite all people to vote (non binding) on this RC. We would like to provide a release that is supported by the majority of our project members. [ ] +1 Release this package as Apache OpenOffice 4.1.0 Beta [ ] 0 Don't care [ ] -1 Do not release this package because... (1) the upload for the Linux 32 bit artifacts is still ongoing, but 64 bit is already available. - 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
Link to Beta-SDK is broken
Hi, on https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds the link to SDK is broken. It is http://ci.apache.org/projects/openoffice/milestones/4.1.0-beta/binaries/SDK/Apache_OpenOffice-Beta-SDK_4.1.0_Win_x86_install_en-US.exe but should be http://ci.apache.org/projects/openoffice/milestones/4.1.0-beta/binaries/SDK/Apache_OpenOffice_Beta-SDK_4.1.0_Win_x86_install_en-US.exe Notice the hyphen between OpenOffice and Beta. It should be a underscore. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Link to Beta-SDK is broken
On 3/6/14 4:47 PM, Regina Henschel wrote: > Hi, > > on > https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds > > the link to SDK is broken. > > It is > http://ci.apache.org/projects/openoffice/milestones/4.1.0-beta/binaries/SDK/Apache_OpenOffice-Beta-SDK_4.1.0_Win_x86_install_en-US.exe > > > but should be > http://ci.apache.org/projects/openoffice/milestones/4.1.0-beta/binaries/SDK/Apache_OpenOffice_Beta-SDK_4.1.0_Win_x86_install_en-US.exe > > > Notice the hyphen between OpenOffice and Beta. It should be a underscore. you are correct, it seems that I forget one place ... I change it and hope confluence wiki let me save it ;-) Juergen > > Kind regards > Regina > > - > 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 Apache OpenOffice 4.1.0 Beta (RC)
+1 On Thu, Mar 6, 2014 at 12:55 AM, Jürgen Schmidt wrote: > Hi all, > > this is a call for vote on releasing the available release candidate > (RC) as Apache OpenOffice 4.1.0 Beta. The Beta release is intended to > reach more early adopters and to receive more valuable feedback to > improve potentially critical areas for the final release. > > Apache OpenOffice 4.1 is a minor update with many bugfixes and at least > 2 major improvements. It's the first version where we have the > iAccessibility2 support integrated and available. A very huge step > forward to reach and better support disabled users especially on > Windows. The second improvement is the switch to 64 bit on MacOS. A long > and overdue "must do" shift forward to support newer APIs (replace > deprecated APIs) and platforms on MacOS. > And we can provide again more complete UI translations and have now > support for 37 languages. New languages for this release compared to > 4.0.1 are Bulgarian, Danish, Hindi, Norwegian Bokmal and Thai. > > Apache OpenOffice 4.1 will be a further key milestone to continue the > success of OpenOffice. > > An overview of release issues can be found under: > > > http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_Beta_fixes.html > > The release candidate artifacts (1) (source release, as well as binary > releases for 37 languages) and further information how to verify and > review Apache OpenOffice 4.1.0 Beta can be found on the following wiki > page: > > > https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds > > The RC is based on the release branch AOO410, revision 1573601! And a > fresh and clean RAT scan output of this revision can be found under > > > http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_RAT_Scan.html > > Please vote on releasing this package as Apache OpenOffice 4.1.0 Beta > > The vote starts now and will be open until: > >Sunday evening, 9 March: 2014-03-09 11:00pm UTC. > > But we invite all people to vote (non binding) on this RC. We would like > to provide a release that is supported by the majority of our project > members. > >[ ] +1 Release this package as Apache OpenOffice 4.1.0 Beta >[ ] 0 Don't care >[ ] -1 Do not release this package because... > > > > (1) the upload for the Linux 32 bit artifacts is still ongoing, but 64 > bit is already available. > > - > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org > For additional commands, e-mail: qa-h...@openoffice.apache.org > >
Link to Beta RC - language packs for Mac OS broken
The links to Beta RC - language packs for Macs is broken. I get "No Such Resource File not found." message. Tried several languages besides the one I wanted. -- _ 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: Link to Beta RC - language packs for Mac OS broken
Hi, Larry Gusaas schrieb: The links to Beta RC - language packs for Macs is broken. I get "No Such Resource File not found." message. Tried several languages besides the one I wanted. The link has MacOS_x86_langpack but the file has MacOS_x86-64_langpack Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Link to Beta-SDK is broken
On Thu, Mar 6, 2014 at 7:59 AM, Jürgen Schmidt wrote: > On 3/6/14 4:47 PM, Regina Henschel wrote: > > Hi, > > > > on > > > https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds > > > > the link to SDK is broken. > > > > It is > > > http://ci.apache.org/projects/openoffice/milestones/4.1.0-beta/binaries/SDK/Apache_OpenOffice-Beta-SDK_4.1.0_Win_x86_install_en-US.exe > > > > > > but should be > > > http://ci.apache.org/projects/openoffice/milestones/4.1.0-beta/binaries/SDK/Apache_OpenOffice_Beta-SDK_4.1.0_Win_x86_install_en-US.exe > > > > > > Notice the hyphen between OpenOffice and Beta. It should be a underscore. > > you are correct, it seems that I forget one place ... I change it and > hope confluence wiki let me save it ;-) > > Juergen > > > > > Kind regards > > Regina > > > > - > > 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 > > It seems the URLS for Linux RPM distributions in -- https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds are incorrect in the table also and need to be changed to: http://ci.apache.org/projects/openoffice/milestones/linux_x86/ instead of: http://people.apache.org/~hdu/developer-snapshots/snapshot/linux_x86/ Thanks. -- - MzK "Cats do not have to be shown how to have a good time, for they are unfailing ingenious in that respect." -- James Mason
Re: Link to Beta-SDK is broken
On 3/6/14 6:15 PM, Kay Schenk wrote: > On Thu, Mar 6, 2014 at 7:59 AM, Jürgen Schmidt wrote: > >> On 3/6/14 4:47 PM, Regina Henschel wrote: >>> Hi, >>> >>> on >>> >> https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds >>> >>> the link to SDK is broken. >>> >>> It is >>> >> http://ci.apache.org/projects/openoffice/milestones/4.1.0-beta/binaries/SDK/Apache_OpenOffice-Beta-SDK_4.1.0_Win_x86_install_en-US.exe >>> >>> >>> but should be >>> >> http://ci.apache.org/projects/openoffice/milestones/4.1.0-beta/binaries/SDK/Apache_OpenOffice_Beta-SDK_4.1.0_Win_x86_install_en-US.exe >>> >>> >>> Notice the hyphen between OpenOffice and Beta. It should be a underscore. >> >> you are correct, it seems that I forget one place ... I change it and >> hope confluence wiki let me save it ;-) >> >> Juergen >> >>> >>> Kind regards >>> Regina >>> >>> - >>> 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 >> >> > It seems the URLS for Linux RPM distributions in -- > > https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds > > are incorrect in the table also and need to be changed to: > > http://ci.apache.org/projects/openoffice/milestones/linux_x86/ > > instead of: > > http://people.apache.org/~hdu/developer-snapshots/snapshot/linux_x86/ > > Thanks. I hope I have fixed now all problems, some stupid mistakes on my side. Jueergen > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Calculate file checksums via Javascript
Interesting page: https://md5file.com/calculator It does MD5/SHA1/SHA256 calculations on local files, using Javascript. Requires HTML5 file support, but that is more common today. No server support is needed, all calculations are done in the browser. Give this as a proof of concept, the interesting next step would be to have a page where users could check the integrity of their AOO downloads. This could be used to check for suspected partial downloads or for suspicions of modified versions. -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE][DISCUSS] How to download AOO 4.1.0 Beta?
Am 03/06/2014 01:19 PM, schrieb Jürgen Schmidt: On 3/6/14 9:20 AM, Jürgen Schmidt wrote: On 3/5/14 10:46 PM, Marcus (OOo) wrote: Am 03/04/2014 07:31 AM, schrieb Jürgen Schmidt: On 3/3/14 9:24 PM, Marcus (OOo) wrote: Am 02/14/2014 09:53 PM, schrieb Marcus (OOo): As this is our first beta release at Apache, I would like to clarify some things before it's maybe too late to change the facts and to prepare webpages: 3. File names: Of course the file names of the install files have to show a difference compared to the general release files. Suggestion: Apache_OpenOffice_4.1.0_Beta_Win_x86_install.exe *If* there is a need to publish another round, it could be extended with a number like: Apache_OpenOffice_4.1.0_Beta2_Win_x86_install.exe OK, I've learned that this won't be possible and the names will be slightly different - but only as long as they are not uploaded to Sourceforge. Therefore I suggest to rename them to the synxtax that was used before (see above). I've created already a little shell script to do the work but won't attach here. @Juergen: Is this something for you? no and I am not in favor or changing the names. I would like to use the names as they came out of the build. Please point me to the scripts that build the name for the download. It should be easy to put the beta string in the correct position. You want to edit the download scripting but not doing a 1 minute file renaming? Hm ;-) I said that I would like to use the bits that comes out of the build process directly without any further touching. We have already said why the naming scheme is different and that it requires more time to analyze and tweak the build process for a proper naming. We hope that we can cleanup and improve this for the next release. I have not asked to change the names in the build system but what comes out of it. I know that but every extra step in the release phase that is not necessary shoudl be avoided. Changing the download script should be trivial as well. Nobody can say if we really will work on this cleanup and time for it. That means tweak the existing process to the names the build produce and not introduce a further step. But for now I would like to avoid any extra step and the change in the download script is one place. Otherwise I have to change several places where I automate some pre-release steps. So, it seems you or me have to change something in order to get working download. OK, don't worry I'll take care of it. again, point us to the relevant scripts or better to the place where I can find instructions to do that for cases where you are not available. an overview of the Beta files can found under http://people.apache.org/~jsc/test/4.1.0-beta_files.txt IT is not yet 100% complete because the Linux upload is still ongoing. I will update it asap Thanks a lot :-) I will look for the missing files. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Close, but not quite 100 million...
I can see what I can do tonight after I do another icon. I should do a design so that I can update the twitter, google+ and facebook profile as well when that happens. We would have that graphic ready on the social media backgrounds before we make the posts on them saying saying [yay 1,000,000 downloads], possibly with the Get It Here version in the post itself. I'm thinking "depict growth" my idea is a background made of soft stockmarket-like upward-right wisps/lines (no explicit arrows). Incorporate soft greens, and silver maybe. Get It Here (With Get It Here Text) Twitter (Background Only) Google+ (Background Only) Facebook (Background Only) Homepage Header (Smaller Background with Logo Only) General 400x600px for blog etc. On Thu, Mar 6, 2014 at 4:30 AM, Oliver-Rainer Wittmann wrote: > Hi, > > > On 05.03.2014 20:47, Rob Weir wrote: >> >> If you look at the SourceForge page you'll see that shows 99.7 million >> downloads: >> >> >> http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline?dates=2011-11-29+to+2014-03-18 >> >> But that number includes the downloads of Language Packs. The more >> conservative number that we report on the blog has always been the >> number of full product downloads. So if someone downloads AOO and >> also downloaded a Language Pack it would be counted as only a single >> download. >> >> The number of full-product downloads is around 95 million. So we >> still have a little more to go before we pop the champagne. Maybe >> around ApacheCon next month we'll hit 1 million. Sooner if we count >> beta downloads, but I'd recommend against counting beta downloads. >> > > Beta downloads should not be counted for the overall download statistic. > > But, the number of Beta downloads will be quite interesting in order to > assess the general interest in such Beta release is. > > Best regards, Oliver. > >> In any case, it is not too early to start thinking about what we want >> to do to publicize the 100 million number, when we do hit it. >> >> We'll do a blog post, of course. It would be awesome if we could >> design a special "100,000,000 downloads" logo that we could use on the >> website. Also, some better looking infographics would be nice. You >> can see what I typically produce, rather bland charts more suitable >> for a scientific report: >> >> https://blogs.apache.org/OOo/entry/75_million_downloads_of_apache >> >> I'm sure someone with more design sense could make something much >> better with the data. (and of course I can provide the updated data) >> >> Any other ideas? >> >> -Rob >> >> - >> 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: [RELEASE][DISCUSS] How to download AOO 4.1.0 Beta?
Am 03/06/2014 09:20 AM, schrieb Jürgen Schmidt: On 3/5/14 10:46 PM, Marcus (OOo) wrote: Am 03/04/2014 07:31 AM, schrieb Jürgen Schmidt: On 3/3/14 9:24 PM, Marcus (OOo) wrote: Am 02/14/2014 09:53 PM, schrieb Marcus (OOo): As this is our first beta release at Apache, I would like to clarify some things before it's maybe too late to change the facts and to prepare webpages: 3. File names: Of course the file names of the install files have to show a difference compared to the general release files. Suggestion: Apache_OpenOffice_4.1.0_Beta_Win_x86_install.exe *If* there is a need to publish another round, it could be extended with a number like: Apache_OpenOffice_4.1.0_Beta2_Win_x86_install.exe OK, I've learned that this won't be possible and the names will be slightly different - but only as long as they are not uploaded to Sourceforge. Therefore I suggest to rename them to the synxtax that was used before (see above). I've created already a little shell script to do the work but won't attach here. @Juergen: Is this something for you? no and I am not in favor or changing the names. I would like to use the names as they came out of the build. Please point me to the scripts that build the name for the download. It should be easy to put the beta string in the correct position. You want to edit the download scripting but not doing a 1 minute file renaming? Hm ;-) I said that I would like to use the bits that comes out of the build process directly without any further touching. We have already said why the naming scheme is different and that it requires more time to analyze and tweak the build process for a proper naming. We hope that we can cleanup and improve this for the next release. I have not asked to change the names in the build system but what comes out of it. I know that but every extra step in the release phase that is not necessary shoudl be avoided. Changing the download script should be trivial as well. Nobody can say if we really will work on this cleanup and time for it. That means tweak the existing process to the names the build produce and not introduce a further step. But for now I would like to avoid any extra step and the change in the download script is one place. Otherwise I have to change several places where I automate some pre-release steps. So, it seems you or me have to change something in order to get working download. OK, don't worry I'll take care of it. again, point us to the relevant scripts or better to the place where I can find instructions to do that for cases where you are not available. I said already I'll take care of it and I will be available on Monday. ;-) Of course it is not that difficult to adapt the scripting to the new naming schema. However, we will then have 2 schemas and needs to differenciate between 4.0.1 and 4.1.0. I've nearly finished the work. If you want to have a look, it's the download.js and download_other.js files. But I've not yet committed the changes. Marcus - 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.0 Beta (RC)
+1 On Fri, Mar 7, 2014 at 12:43 AM, Sandhya Sivakumar wrote: > +1 > > > On Thu, Mar 6, 2014 at 12:55 AM, Jürgen Schmidt >wrote: > > > Hi all, > > > > this is a call for vote on releasing the available release candidate > > (RC) as Apache OpenOffice 4.1.0 Beta. The Beta release is intended to > > reach more early adopters and to receive more valuable feedback to > > improve potentially critical areas for the final release. > > > > Apache OpenOffice 4.1 is a minor update with many bugfixes and at least > > 2 major improvements. It's the first version where we have the > > iAccessibility2 support integrated and available. A very huge step > > forward to reach and better support disabled users especially on > > Windows. The second improvement is the switch to 64 bit on MacOS. A long > > and overdue "must do" shift forward to support newer APIs (replace > > deprecated APIs) and platforms on MacOS. > > And we can provide again more complete UI translations and have now > > support for 37 languages. New languages for this release compared to > > 4.0.1 are Bulgarian, Danish, Hindi, Norwegian Bokmal and Thai. > > > > Apache OpenOffice 4.1 will be a further key milestone to continue the > > success of OpenOffice. > > > > An overview of release issues can be found under: > > > > > > > http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_Beta_fixes.html > > > > The release candidate artifacts (1) (source release, as well as binary > > releases for 37 languages) and further information how to verify and > > review Apache OpenOffice 4.1.0 Beta can be found on the following wiki > > page: > > > > > > > https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds > > > > The RC is based on the release branch AOO410, revision 1573601! And a > > fresh and clean RAT scan output of this revision can be found under > > > > > > > http://people.apache.org/~jsc/developer-snapshots/snapshot/AOO4.1.0_RAT_Scan.html > > > > Please vote on releasing this package as Apache OpenOffice 4.1.0 Beta > > > > The vote starts now and will be open until: > > > >Sunday evening, 9 March: 2014-03-09 11:00pm UTC. > > > > But we invite all people to vote (non binding) on this RC. We would like > > to provide a release that is supported by the majority of our project > > members. > > > >[ ] +1 Release this package as Apache OpenOffice 4.1.0 Beta > >[ ] 0 Don't care > >[ ] -1 Do not release this package because... > > > > > > > > (1) the upload for the Linux 32 bit artifacts is still ongoing, but 64 > > bit is already available. > > > > - > > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: qa-h...@openoffice.apache.org > > > > > -- Best Regards, Steve Yin
Re: Help with the Extentions
These are the extensions that I have downloaded Office SVG 1.0 Professional Template Pack ll- English 1.0nloaded, I clicked on the download and then from my downloaded window I doubled click on the download and the extension manager came up and said installing then it showed in the extension manager file. Thank you - Original Message - From: "Dave Barton" To: dev@openoffice.apache.org Cc: careaboob...@comcast.net Sent: Tuesday, March 4, 2014 3:04:33 AM Subject: Re: Help with the Extentions Original Message From: careaboob...@comcast.net To: dev@openoffice.apache.org Date: Mon, 3 Mar 2014 23:37:08 + (UTC) > I have downloaded some extensions and I can not figure out how to get started > so I can start using them. I have installed them. > > Carrie A. Williams Hi Carrie, You need to tell us which extensions and how (eg. using the "Extension Manager") you installed them. This will enable us to help you get started. Please only reply to dev@openoffice.apache.org Dave
