CMS diff:
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/stats%2Fdefects.txt Yan Ji Index: trunk/content/stats/defects.txt === --- trunk/content/stats/defects.txt (revision 1465315) +++ trunk/content/stats/defects.txt (working copy) @@ -21,3 +21,4 @@ 2013-01-01,2755,832 2013-02-01,2864,898 2013-03-01,2973,981 +2013-04-01,3069,1041 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: LanguageTool have problems on dev builds (no context menu suggestions)
RGB ES wrote: I just noticed that the LanguageTool extension(1) have some problems on both, the latest builds from the build bot and the one layer build from Jürgen, but it works without issues on 3.4.1 so it's not a problem with the extension but with AOO. It's not necessarily a problem in OpenOffice; it might be that LanguageTool has problems with some backwards-incompatible changes done in OpenOffice. To start, I would recommend to make the extension developers aware of it: http://www.languagetool.org/ asking them to write to this list if they need additional information. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [QA][Weekly Report] Defects Status weekly report as of 2013/04/08
2013/4/7 Yi Xuan Liu : > Defects status weekly report as of 20130408: > http://wiki.openoffice.org/wiki/QA/Report/DefectStatus#Weekly_report_as_of_2013.2F04.2F08 I thought nice disseminate on social networking: http://identi.ca/notice/100521297 Albino - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: LanguageTool have problems on dev builds (no context menu suggestions)
2013/4/7 Andrea Pescetti > RGB ES wrote: > >> I just noticed that the LanguageTool extension(1) have some problems on >> both, the latest builds from the build bot and the one layer build from >> Jürgen, but it works without issues on 3.4.1 so it's not a problem with >> the >> extension but with AOO. >> > > It's not necessarily a problem in OpenOffice; it might be that > LanguageTool has problems with some backwards-incompatible changes done in > OpenOffice. To start, I would recommend to make the extension developers > aware of it: http://www.languagetool.org/ asking them to write to this > list if they need additional information. > OK, I've sent an email to one of the main developers. Regards Ricardo > > Regards, > Andrea. > > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@openoffice.**apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: LanguageTool have problems on dev builds (no context menu suggestions)
2013/4/7 Andrea Pescetti > RGB ES wrote: > >> I just noticed that the LanguageTool extension(1) have some problems on >> both, the latest builds from the build bot and the one layer build from >> Jürgen, but it works without issues on 3.4.1 so it's not a problem with >> the >> extension but with AOO. >> > > It's not necessarily a problem in OpenOffice; it might be that > LanguageTool has problems with some backwards-incompatible changes done in > OpenOffice. There is list of those changes? The release notes talks about an unified menu API and points to this issue https://issues.apache.org/ooo/show_bug.cgi?id=121542 but I'm not sure about the meaning of that. Regards Ricardo > To start, I would recommend to make the extension developers aware of it: > http://www.languagetool.org/ asking them to write to this list if they > need additional information. > > Regards, > Andrea. > > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@openoffice.**apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: LanguageTool have problems on dev builds (no context menu suggestions)
Hi Ricardo, On Sun, Apr 07, 2013 at 03:18:11PM +0200, RGB ES wrote: > 2013/4/7 Andrea Pescetti > > > RGB ES wrote: > > > >> I just noticed that the LanguageTool extension(1) have some problems on > >> both, the latest builds from the build bot and the one layer build from > >> Jürgen, but it works without issues on 3.4.1 so it's not a problem with > >> the > >> extension but with AOO. > >> > > > > It's not necessarily a problem in OpenOffice; it might be that > > LanguageTool has problems with some backwards-incompatible changes done in > > OpenOffice. > > > There is list of those changes? The release notes talks about an unified > menu API and points to this issue > > https://issues.apache.org/ooo/show_bug.cgi?id=121542 > > but I'm not sure about the meaning of that. This API change is completely unrelated to grammar checking. Please open a bug, this is also reproducible with http://extensions.openoffice.org/project/lightproof so the regression is in AOO code. Regards -- Ariel Constenla-Haile La Plata, Argentina pgpOVUKEuPYTN.pgp Description: PGP signature
Re: LanguageTool have problems on dev builds (no context menu suggestions)
2013/4/7 Ariel Constenla-Haile > Hi Ricardo, > > On Sun, Apr 07, 2013 at 03:18:11PM +0200, RGB ES wrote: > > 2013/4/7 Andrea Pescetti > > > > > RGB ES wrote: > > > > > >> I just noticed that the LanguageTool extension(1) have some problems > on > > >> both, the latest builds from the build bot and the one layer build > from > > >> Jürgen, but it works without issues on 3.4.1 so it's not a problem > with > > >> the > > >> extension but with AOO. > > >> > > > > > > It's not necessarily a problem in OpenOffice; it might be that > > > LanguageTool has problems with some backwards-incompatible changes > done in > > > OpenOffice. > > > > > > There is list of those changes? The release notes talks about an unified > > menu API and points to this issue > > > > https://issues.apache.org/ooo/show_bug.cgi?id=121542 > > > > but I'm not sure about the meaning of that. > > This API change is completely unrelated to grammar checking. Please open > a bug, this is also reproducible with > http://extensions.openoffice.org/project/lightproof > so the regression is in AOO code. > OK, it is filled here: https://issues.apache.org/ooo/show_bug.cgi?id=122015 I used Writer/UI as Product/Component. Regards Ricardo > > > Regards > -- > Ariel Constenla-Haile > La Plata, Argentina >
Customized builds
I wonder if the nightly builds support customized builds, if for example if a user wants a build that has some special configuration like, anti-alias by default or a customized default templates or menu layout. Can the nightly build infrastructure be used to generate that? If not, why not, what would be needed to do that. Regards. -- Alexandro Colorado Apache OpenOffice Contributor http://es.openoffice.org
Re: Customized builds
On 7 April 2013 20:58, Alexandro Colorado wrote: > I wonder if the nightly builds support customized builds, if for example if > a user wants a build that has some special configuration like, anti-alias > by default or a customized default templates or menu layout. > > Can the nightly build infrastructure be used to generate that? > No, our buildbot's run with a preconfigured setup, including number of tasks and configure for each task (job). > > If not, why not, what would be needed to do that. > We would need to change away from build bot, it cannot support dynamic. All changes in the setup has to be done via the infrastructure svn, where only a few have access. But I dont really get, if a user wants a customized build, would it not be simpler for him to build it himself ? the nightly build are in my opinion to secure that our product builds and that the branches compile on different platforms. The purpose of the nightly build is not to save the user from installing a compiler. rgds jan I. > > Regards. > > > -- > Alexandro Colorado > Apache OpenOffice Contributor > http://es.openoffice.org >
Re: Customized builds
On Sun, Apr 7, 2013 at 2:12 PM, janI wrote: > On 7 April 2013 20:58, Alexandro Colorado wrote: > > > I wonder if the nightly builds support customized builds, if for example > if > > a user wants a build that has some special configuration like, anti-alias > > by default or a customized default templates or menu layout. > > > > Can the nightly build infrastructure be used to generate that? > > > No, our buildbot's run with a preconfigured setup, including number of > tasks and configure for each task (job). > > > > > > If not, why not, what would be needed to do that. > > > We would need to change away from build bot, it cannot support dynamic. All > changes in the setup has to be done via the infrastructure svn, where only > a few have access. > > But I dont really get, if a user wants a customized build, would it not be > simpler for him to build it himself ? the nightly build are in my opinion > Well because a user might want to just click on a build made by an automated bot. This is done a lot by OpenSuSE studio people which can let you remaster SuSE through a web interface and download the .iso, virtual machine or amazon image. > to secure that our product builds and that the branches compile on > different platforms. The purpose of the nightly build is not to save the > user from installing a compiler. > > rgds > jan I. > > > > > Regards. > > > > > > -- > > Alexandro Colorado > > Apache OpenOffice Contributor > > http://es.openoffice.org > > > -- Alexandro Colorado Apache OpenOffice Contributor http://es.openoffice.org
Re: Customized builds
On 7 April 2013 21:24, Alexandro Colorado wrote: > On Sun, Apr 7, 2013 at 2:12 PM, janI wrote: > > > On 7 April 2013 20:58, Alexandro Colorado wrote: > > > > > I wonder if the nightly builds support customized builds, if for > example > > if > > > a user wants a build that has some special configuration like, > anti-alias > > > by default or a customized default templates or menu layout. > > > > > > Can the nightly build infrastructure be used to generate that? > > > > > No, our buildbot's run with a preconfigured setup, including number of > > tasks and configure for each task (job). > > > > > > > > > > If not, why not, what would be needed to do that. > > > > > We would need to change away from build bot, it cannot support dynamic. > All > > changes in the setup has to be done via the infrastructure svn, where > only > > a few have access. > > > > But I dont really get, if a user wants a customized build, would it not > be > > simpler for him to build it himself ? the nightly build are in my opinion > > > > Well because a user might want to just click on a build made by an > automated bot. > > This is done a lot by OpenSuSE studio people which can let you remaster > SuSE through a web interface and download the .iso, virtual machine or > amazon image. > I can understand the need for an OS, but do we really want to "distribute" different packages. The binary we deliver, have quite a lot of options for configuration. I admit, that I think a lot more in reducing the compile switches (a la, this is our binary, all compile options are solely for our developers/testers)if a compile switch is usefull to a user, it should be an option in the program instead. rgds jan I. > > > > to secure that our product builds and that the branches compile on > > different platforms. The purpose of the nightly build is not to save the > > user from installing a compiler. > > > > rgds > > jan I. > > > > > > > > Regards. > > > > > > > > > -- > > > Alexandro Colorado > > > Apache OpenOffice Contributor > > > http://es.openoffice.org > > > > > > > > > -- > Alexandro Colorado > Apache OpenOffice Contributor > http://es.openoffice.org >
Re: Customized builds
On Sun, Apr 7, 2013 at 2:48 PM, janI wrote: > On 7 April 2013 21:24, Alexandro Colorado wrote: > > > On Sun, Apr 7, 2013 at 2:12 PM, janI wrote: > > > > > On 7 April 2013 20:58, Alexandro Colorado wrote: > > > > > > > I wonder if the nightly builds support customized builds, if for > > example > > > if > > > > a user wants a build that has some special configuration like, > > anti-alias > > > > by default or a customized default templates or menu layout. > > > > > > > > Can the nightly build infrastructure be used to generate that? > > > > > > > No, our buildbot's run with a preconfigured setup, including number of > > > tasks and configure for each task (job). > > > > > > > > > > > > > > If not, why not, what would be needed to do that. > > > > > > > We would need to change away from build bot, it cannot support dynamic. > > All > > > changes in the setup has to be done via the infrastructure svn, where > > only > > > a few have access. > > > > > > But I dont really get, if a user wants a customized build, would it not > > be > > > simpler for him to build it himself ? the nightly build are in my > opinion > > > > > > > Well because a user might want to just click on a build made by an > > automated bot. > > > > This is done a lot by OpenSuSE studio people which can let you remaster > > SuSE through a web interface and download the .iso, virtual machine or > > amazon image. > > > I can understand the need for an OS, but do we really want to "distribute" > different packages. The binary we deliver, have quite a lot of options for > configuration. > > I admit, that I think a lot more in reducing the compile switches (a la, > this is our binary, all compile options are solely for our > developers/testers)if a compile switch is usefull to a user, it should > be an option in the program instead. > The question came from a user that wonder how difficult would it be to remaster a binary of AOO 'in the cloud' which made me think of the nightly builds. But I understand this is more challenging that at first glance. i guess if this was trivial, l10n would have used long ago instead of waiting for a localized version. > > rgds > jan I. > > > > > > > > to secure that our product builds and that the branches compile on > > > different platforms. The purpose of the nightly build is not to save > the > > > user from installing a compiler. > > > > > > rgds > > > jan I. > > > > > > > > > > > Regards. > > > > > > > > > > > > -- > > > > Alexandro Colorado > > > > Apache OpenOffice Contributor > > > > http://es.openoffice.org > > > > > > > > > > > > > > > -- > > Alexandro Colorado > > Apache OpenOffice Contributor > > http://es.openoffice.org > > > -- Alexandro Colorado Apache OpenOffice Contributor http://es.openoffice.org
OpenOffice blog planets all dead - is there a new one?
http://www.openoffice.org/editorial/blogs.html This page is seriously out of date. In particular, there's four blog planets listed there, none of which are operational. Is there a new blog planet? Should there be? - d. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OpenOffice blog planets all dead - is there a new one?
"Seriously out of date" is an understatement. We're almost talking archeology here. I haven't maintained that page in years, and the one that is most relevant is probably here, https://blogs.apache.org/OOo/, but it's not a planet. louis On 7 April 2013 18:42, David Gerard wrote: > http://www.openoffice.org/editorial/blogs.html > > This page is seriously out of date. In particular, there's four blog > planets listed there, none of which are operational. Is there a new > blog planet? Should there be? > > > - d. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: OpenOffice blog planets all dead - is there a new one?
2013/4/8 David Gerard > http://www.openoffice.org/editorial/blogs.html > > This page is seriously out of date. In particular, there's four blog > planets listed there, none of which are operational. Is there a new > blog planet? Should there be? > Exactly one year ago there was a thread about a "planet AOO": http://markmail.org/message/u4qxggwpfgw4ij2h Regards Ricardo > > > - d. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: OpenOffice blog planets all dead - is there a new one?
On Sun, Apr 7, 2013 at 7:01 PM, Louis Suárez-Potts wrote: > "Seriously out of date" is an understatement. We're almost talking > archeology here. I haven't maintained that page in years, and the one that > is most relevant is probably here, https://blogs.apache.org/OOo/, but it's > not a planet. > louis > > Fortunately that is the blog we link to prominently from our website. The http://www.openoffice.org/editorial/blogs.html page David found is almost invisible to users, since it is not prominently linked from anywhere, onsite or off. In the last 30 days it has received only 158 visits, out of over 6 million visits to the website. So it is not the highest on my list of webpages to worry about. That said, all committers are able to get their personal blogs aggregated into the Apache Committers Planet: http://planet.apache.org/committers/ And if we want to have an OpenOffice-specifc version of this it would not be too difficult to do. -Rob > > On 7 April 2013 18:42, David Gerard wrote: > > > http://www.openoffice.org/editorial/blogs.html > > > > This page is seriously out of date. In particular, there's four blog > > planets listed there, none of which are operational. Is there a new > > blog planet? Should there be? > > > > > > - d. > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > >
Re: CMS diff:
Thanks for the patch. I've checked it in. -Rob On Sun, Apr 7, 2013 at 4:03 AM, Yan Ji wrote: > Clone URL (Committers only): > > https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/stats%2Fdefects.txt > > Yan Ji > > Index: trunk/content/stats/defects.txt > === > --- trunk/content/stats/defects.txt (revision 1465315) > +++ trunk/content/stats/defects.txt (working copy) > @@ -21,3 +21,4 @@ > 2013-01-01,2755,832 > 2013-02-01,2864,898 > 2013-03-01,2973,981 > +2013-04-01,3069,1041 > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: OS for main AOO buildbots
Hi Kay, On Tue, Apr 02, 2013 at 04:33:05PM -0700, Kay Schenk wrote: > Well, Ok. I think we need to maintain a secure environment with > anything used for our builds -- libraries, etc. That would be my only > concern with "older" items. CentOS 5 is currently being maintained; in fact, the "latest and greatest" 5 version has been released on January 2013 http://lists.centos.org/pipermail/centos-announce/2013-January/019205.html CentOS 5 will get full updates until Q1 2014, and maintenance updates until March 31st, 2017 http://wiki.centos.org/About/Product http://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d This means there will be security and other critical bug fixes until 2017, while maintaining the kernel and glibc base (2.6.18 and 2.5, respectively). You won't find this in other distros, not even Debian (squeeze has glibc-2.11 http://packages.debian.org/squeeze/glibc-2.11-1), which is known for "stability than cutting-edge packages". Regards -- Ariel Constenla-Haile La Plata, Argentina pgpAhAYr6DweN.pgp Description: PGP signature
Re: Customized builds
On 4/7/13 9:58 PM, Alexandro Colorado wrote: > On Sun, Apr 7, 2013 at 2:48 PM, janI wrote: > >> On 7 April 2013 21:24, Alexandro Colorado wrote: >> >>> On Sun, Apr 7, 2013 at 2:12 PM, janI wrote: >>> On 7 April 2013 20:58, Alexandro Colorado wrote: > I wonder if the nightly builds support customized builds, if for >>> example if > a user wants a build that has some special configuration like, >>> anti-alias > by default or a customized default templates or menu layout. > > Can the nightly build infrastructure be used to generate that? > No, our buildbot's run with a preconfigured setup, including number of tasks and configure for each task (job). > > If not, why not, what would be needed to do that. > We would need to change away from build bot, it cannot support dynamic. >>> All changes in the setup has to be done via the infrastructure svn, where >>> only a few have access. But I dont really get, if a user wants a customized build, would it not >>> be simpler for him to build it himself ? the nightly build are in my >> opinion >>> >>> Well because a user might want to just click on a build made by an >>> automated bot. >>> >>> This is done a lot by OpenSuSE studio people which can let you remaster >>> SuSE through a web interface and download the .iso, virtual machine or >>> amazon image. >>> >> I can understand the need for an OS, but do we really want to "distribute" >> different packages. The binary we deliver, have quite a lot of options for >> configuration. >> >> I admit, that I think a lot more in reducing the compile switches (a la, >> this is our binary, all compile options are solely for our >> developers/testers)if a compile switch is usefull to a user, it should >> be an option in the program instead. >> > > The question came from a user that wonder how difficult would it be to > remaster a binary of AOO 'in the cloud' which made me think of the nightly > builds. But I understand this is more challenging that at first glance. i > guess if this was trivial, l10n would have used long ago instead of waiting > for a localized version. > > Well the idea in general is not a bad one. But I would think more in the direction of customized packaging. Means if some body needs only a writer and dependencies in French, he can click on some options and can later on download a new packaged french writer version. Together with a good update mechanism and a stable and secure infra structure supporting such a service it can be interesting. But we are far away from this in many areas and we have far more important things that can benefit from some activity. Juergen > >> >> rgds >> jan I. >> >>> >>> to secure that our product builds and that the branches compile on different platforms. The purpose of the nightly build is not to save >> the user from installing a compiler. rgds jan I. > > Regards. > > > -- > Alexandro Colorado > Apache OpenOffice Contributor > http://es.openoffice.org > >>> >>> >>> >>> -- >>> Alexandro Colorado >>> Apache OpenOffice Contributor >>> http://es.openoffice.org >>> >> > > > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
