Re: Build and unit test errors with cppunit
On Mon, Aug 24, 2015 at 8:25 PM, Damjan Jovanovic damjan@gmail.com wrote: On Mon, Aug 24, 2015 at 11:36 PM, Kay Schenk kay.sch...@gmail.com wrote: On 08/24/2015 01:04 PM, Damjan Jovanovic wrote: Hi Since commit 1536730 on 2013-10-29 by alg (Armin Le Grand), AOO hasn't been able to compile with cppunit present and enabled (--with-system-cppunit), as at least the basegfx and basebmp modules both have compile errors and unit test failures. I fixed the basegfx compile errors (brackets in wrong places and extraneous commas in function arguments) in commits 1697461 and 1697470, but then 6 basegfx units tests still fail, and if I comment them out, the build fails later with compile errors in basebmp, which are more complicated as new 3rd and 4th arguments to the basegfx::tools::importFromSvgD() function are necessary and I am not sure what they should be. Please help. Also why hasn't anybody caught this earlier? Do we not usually compile AOO with cppunit enabled? I think the answer to this is no. See a post from a few years ago-- http://markmail.org/message/kmkv7cr5todacdq6 It seems we need some code cleanup to remove the remaining cppunit references. Thank you Damjan If you don't specify anything about cppunit in your config options, you will get a warning that cpppunit will not be used, and thus, no errors. See, for example, config output from linux-32 buildbot -- https://ci.apache.org/builders/openoffice-linux32-nightly/builds/63/steps/configure/logs/stdio Thank you, but the reason I used --with-system-cppunit in the first place is because I am trying to develop a unit test for a patch I am working on. If I can't make a new unit test under /main/module/test, what can I put it into then?The UNO tests under /main/module/qa and /main/qadevOOo? The UI tests under /test? Do we have any others? Hi, Damjan-- Pedro was on the right track! Google Test has been integrated into the AOO framework and that is to be used instead of CPPUNIT. My apologies for not keeping up with this. Details: http://www.mail-archive.com/dev%40openoffice.apache.org/msg18808.html I don't know how much usage this has gotten since June, 2014 so please keep us informed about your experience. -- - MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu
RE: 2015-08-24 Future Board Reports
Great question, Louis. The board-reporting guidelines are quite comprehensive, http://apache.org/foundation/board/reporting. Please note the final section, Engaging with the Board about the Report. It is not until the Board meeting that the report is accepted, after any requested changes, and there may be action items back through Chair that also arise out of the Board meeting. The Apache OpenOffice collection of Board Reports is at https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports. You'll see that the latest one is a draft, and the template being used is evident. The first report from Apache OpenOffice as a Top Level Project is the one for 2012 Nov. Notice that the Board Minutes, after approval at the next Board Meeting, are published as a single text file with all of the reports from Projects attached. Here are the approved minutes that include the July 2015 report for Apache OpenOffice: http://www.apache.org/foundation/records/minutes/2015/board_minutes_2015_07_15.txt. The report required no discussion at the meeting and it consists of under 50 lines of text at Attachment AQ. You can also see how other projects report there. - Dennis -Original Message- From: Louis Suárez-Potts [mailto:lui...@gmail.com] Sent: Monday, August 24, 2015 20:14 To: dev@openoffice.apache.org; Dennis E. Hamilton orc...@apache.org Subject: Re: 2015-08-24 Future Board Reports Dennis, [ ... ] Thanks for the explanation on process. But I ask an intentionally naïve question. What is contained in the Report to the Board? Best, Louis - 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: 2015-08-24 Future Board Reports
I don't know, Simon. I suspect there are a variety of approaches to how reports to the Board are arrived at on Apache Projects. The most visible activity I have seen is on the Incubator PMC, and I suspect that is a level to aspire to. I am also fairly confident that the Chair has great flexibility although it remains the Chair's specific accountability. For substantive matters and issues that don't fall into those few categories that require private treatment at the PMC, I anticipate that the community will be fully apprised, even before any mention in a report to the Board, assuming it needs any Board attention at all. If I, as Chair, fall short in assuring that, it will be evident in any disparity between the accepted Board reports and what the community would find unsurprising. I would expect to be called-out on that and I will clean it up. The Board places great reliance on PMCs to manage affairs at the level where they are the most informed and able to act. I suspect they count on the Chair and the reports to the board as assurance that such reliance is warranted. I will provide more that might be useful to you in my response to the question from Louis Suárez-Potts. - Dennis -Original Message- From: Simon Phipps [mailto:si...@webmink.com] Sent: Tuesday, August 25, 2015 02:07 To: dev dev@openoffice.apache.org; orc...@apache.org Subject: Re: 2015-08-24 Future Board Reports On Tue, Aug 25, 2015 at 4:26 AM, Dennis E. Hamilton orc...@apache.org wrote: Until further notice, the AOO Report to the Board will be developed by the Chair privately with the PMC and will not be made or discussed in public before its submission and acceptance by the Board. Subsequent to that acceptance and its publication by the Board, typically a month later, the final version will also be made available for the information of the full Apache OpenOffice community and as part of the project's historical materials. Please forgive my lack of Apache-wide insight, but is this approach common in other Apache projects or unique to AOO? Thanks, S. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
2015-08-25 When Speaking as the Chair
[BCC to the AOO PMC] From the Chair, It occurs to me that the role of the Chair of the Apache OpenOffice Project Management Committee is often seriously over-estimated. There is also a level of prestige that may be associated with it that tends to give more weight to what I might say than otherwise. It is important for me that others understand that for the most part, the PMC Chair is no different than another member of the PMC, other committers, and the many other contributors in the Apache OpenOffice community. I don't want to have my communications to now be taken with more authority than they would were I not the Chair. So, when I am speaking as the Chair, I will always introduce my emails with From the Chair. That means I am operating in the context of my responsibilities as an Officer of the Foundation. In all other cases, there is no distinction. If it is about PMC matters, it must be regarded as only something any PMC member could do or say. And in all cases, for weighty matters consensus is sought and you will usually know how that has or has not been achieved in the usual way that [PROPOSAL], [DISCUSS], and [VOTE] mail threads are handled. Thank you for the support that I have been offered and the trust you have placed in me as I undertake this new role. - Dennis - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 2015-08-24 Future Board Reports
On Tue, Aug 25, 2015 at 4:26 AM, Dennis E. Hamilton orc...@apache.org wrote: Until further notice, the AOO Report to the Board will be developed by the Chair privately with the PMC and will not be made or discussed in public before its submission and acceptance by the Board. Subsequent to that acceptance and its publication by the Board, typically a month later, the final version will also be made available for the information of the full Apache OpenOffice community and as part of the project's historical materials. Please forgive my lack of Apache-wide insight, but is this approach common in other Apache projects or unique to AOO? Thanks, S.
Starting Introduction to Contributing to Apache OpenOffice Module
Symphony v60
RE: 2015-08-24 Future Board Reports
Thank you Andrea, Your suggestions are valuable to me and I will take them to heart. -Original Message- From: Andrea Pescetti [mailto:pesce...@apache.org] Sent: Tuesday, August 25, 2015 14:44 To: dev@openoffice.apache.org Subject: Re: 2015-08-24 Future Board Reports [ ... ] Can I propose some additions to the process to make sure this ends up in MORE transparency instead of LESS transparency as it might seem? 1) Before the standard quarterly reports, ask the main lists for useful information to include in the report, and ask volunteers to reply on list (then you will assemble the information as you see fit). 2) Continue updating https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports by copying the final report once it is published. 3) At the same time, publish a short blog post at https://blogs.apache.org/OOo/ with an introduction that helps the understanding and a link to the report published in #2. [ ... ] - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 2015-08-25 When Speaking as the Chair
On Tue, 25 Aug 2015, at 06:09 PM, Dennis E. Hamilton wrote: [BCC to the AOO PMC] From the Chair, It occurs to me that the role of the Chair of the Apache OpenOffice Project Management Committee is often seriously over-estimated. There is also a level of prestige that may be associated with it that tends to give more weight to what I might say than otherwise. Why? I really do not get how you might come to that conclusion. As there is no prestige, or weight to be added when doing day-to-day activities. It is important for me that others understand that for the most part, the PMC Chair is no different than another member of the PMC, other committers, and the many other contributors in the Apache OpenOffice community. Exactly! This is in direct contradiction of your opening paragraph. I don't want to have my communications to now be taken with more authority than they would were I not the Chair. For anyone who knows how the ASF works they will know that this is not even possible. As you are no more senior, and therefore carry no more authority. So, when I am speaking as the Chair, I will always introduce my emails with From the Chair. That means I am operating in the context of my responsibilities as an Officer of the Foundation. Wow. I find this whole line of thinking extremely disheartening and quite frankly condescending and disingenuous. It borders on the ludicrous. In all other cases, there is no distinction. If it is about PMC matters, it must be regarded as only something any PMC member could do or say. Again, how does PMC chair change this? It does not. And in all cases, for weighty matters consensus is sought and you will usually know how that has or has not been achieved in the usual way that [PROPOSAL], [DISCUSS], and [VOTE] mail threads are handled. Thank you for the support that I have been offered and the trust you have placed in me as I undertake this new role. I do hope this PMC can see it's way past all this rigmarole and to a lighterweight, flexible and frankly functional (not combative) future. - Dennis Many thanks, -- Tony - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Meta data changes for 4.1.2
On 24/08/2015 Kay Schenk wrote: To get started, please see rev. 1602195 -- https://svn.apache.org/viewvc?view=revisionrevision=1602195 We need changes in version and build number for sure. Anything else? Well, we'll need all of it, plus everything else cited in the issue, like update URLs. The three patches for the basic part are probably easier to understand separately: https://svn.apache.org/viewvc/openoffice/branches/AOO410/main/instsetoo_native/util/openoffice.lst?r1=1583558r2=1602195pathrev=1602195diff_format=h https://svn.apache.org/viewvc/openoffice/branches/AOO410/main/odk/util/makefile.pmk?r1=1571604r2=1602195pathrev=1602195diff_format=h These two are a rather trivial renaming (even if it's done in surprisingly high number of places!). https://svn.apache.org/viewvc/openoffice/branches/AOO410/main/solenv/inc/minor.mk?r1=1587478r2=1602195pathrev=1602195diff_format=h Here I don't know if there is a logic in attributing the new build number. Anything that increases it is likely to work, and 9780 (probably the same one you proposed in another thread) seems reasonable seeing the file history of https://svn.apache.org/viewvc/openoffice/branches/AOO410/main/solenv/inc/minor.mk?diff_format=hview=logpathrev=1602195 I haven't tested it, but I'll try building with the changes described above tomorrow unless someone else does it faster. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 2015-08-24 Future Board Reports
Dennis E. Hamilton wrote: I am changing the practice of development and submission of Reports to the Board. ... I expect working in public to increase greatly, not to diminish I wasn't excited by this new report drafting process at first. Then, reading the full message, I realized that what is public now will still remain public; it will simply be published after the Board meeting instead of before it. Well, the choice on how to develop the report is up to you in the end, and the report should be a collection of information that everybody already knows, as the list at https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports confirms by being terribly boring (and I admit I wrote most of those). In most Apache projects the report is prepared single-handedly by the Chair and published after the Board meeting, so what you propose is actually the norm at Apache. Can I propose some additions to the process to make sure this ends up in MORE transparency instead of LESS transparency as it might seem? 1) Before the standard quarterly reports, ask the main lists for useful information to include in the report, and ask volunteers to reply on list (then you will assemble the information as you see fit). 2) Continue updating https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports by copying the final report once it is published. 3) At the same time, publish a short blog post at https://blogs.apache.org/OOo/ with an introduction that helps the understanding and a link to the report published in #2. Sorry for being bad to the point of suggesting that the new Chair-elect takes care of tasks that of course I never did (except #2) when I was Chair... but I think it is important that we leave no doubt that we want maximum transparency and visibility. Mine are just suggestions on what I would have done if I had had more time available for quarterly reports, of course they can be ignored and I won't be upset at all. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
