[dev] Re: [qa-dev] Re: [dev] proposal for change of cws policies
Hi Michael, Michael Meeks schrieb: Hi Martin, On Thu, 2007-07-05 at 14:14 +0200, Martin Hollmichel wrote: With the help of Nikolai we are now able to provide a proposal for a modified version of the child workspace policies on http://wiki.services.openoffice.org/wiki/CWS_Policies This looks like an improvement :-) thanks. Under the Setting a CWS to approved by QA - since this is something developers can do (for category B) - can you expand on the (should for bug fixes) section - Make a test specification / test case available - is there some repository of such things somewhere ? how is that done ? in what form ? can this be waived in the case that a unit test exercises the code paths ? :-) I can speak for QA on GUI level. We define 'developer issues' (like the ones in Category B) as issues, where it isn't possible to create test case specifications or write test cases for automated testing with TestTool. If my team get such issues (or CWS with such issues), we do general regression testing in the areas where the changes were done. But these issues were tested and still can be tested by another developer by code review or doing unit test or API testing. I cannot speak for Unit test or API testing on issues or CWS. But is this needed to explain in such document? Or what should be include? Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] proposal for change of cws policies
Hi Martin, Martin Hollmichel wrote: I suggest that we make this cws policies official on July 11th if there are no objections until then. I have modified some things in the Wiki without changing or deleting the content or the meaning of it: - We should use the common wording in the community 'issue' instead of 'task' - we have more than one specification: (functional) software specification; test case speification [I have added the links to the chapters inside the Wiki] - Bullet lists are fine but you have priorized the issue categories and I have used an ordered list to make it more clear - A bug fix? A fix is IMO the same (fixing something that goes wrong...); removed the word bug because a fix could also be something that makes an existing behaviour faster/more efficient/ - added links to QA rules, Gatekeeper, EIS, If these changes get accepted I propose to exchange the Level of impact in the EIS application accordingly to the new categorization of cws in the policies. From my point of view more clear than in the past. Cu, Jogi http://qa.openoffice.org/qatesttool http://wiki.services.openoffice.org/wiki/User:Jsi -- Sun Microsystems GmbH Joerg Sievers Nagelsweg 55Quality Assurance Engineer 20097 Hamburg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] proposal for change of cws policies
Hi Peter, Peter Junge wrote: defined wrong. Please refer included link http://wiki.services.openoffice.org/wiki/Approve_a_CWS. Done! Cu, Jogi http://qa.openoffice.org/qatesttool http://wiki.services.openoffice.org/wiki/User:Jsi -- Sun Microsystems GmbH Joerg Sievers Nagelsweg 55Quality Assurance Engineer 20097 Hamburg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] RE:[dev] question about use XStorag
chensuchun wrote: [...] Sorry, there is no OwnSubFilter service in my openoffice, my openoffice is based on the source of OOB680 . [...] Why do you have to use such an old code base? I'd strongly recommend to update to f.e. OOF680 m18, the latest release. From my point of view it does not make sense to do development based on old code. Rüdiger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Bug in determining Java type for UNO_LONG properties ?
Rony G. Flatscher wrote: Hi there, tried to find an entry on this in the issue tracker, but have not been successful. Hence, first asking whether this is a bug in the Java interface to UNO or a misconception on my side. Problem: using a property's' Type attribute (prop.Type) one works with a com.sun.star.uno.Type object (cf. http://api.openoffice.org/docs/java/ref/com/sun/star/uno/Type.html) it seems that for UNO_LONG types (prop.Type.getTypeClass() returns an UNO_LONG TypeClass object), whereas prop.Type.getTypeName returns the string name long instead of int. you get always the UNO type name and not the mapped name for a specific language binding. As a result, using this information to cast Java types to the corresponding UNO type yields a type error as supplying java.lang.Long objects for UNO_LONG properties is not possible, rather java.lang.Integer objects need to be supplied for them. The documentation of com.sun.star.uno.Type is not totally clear for me, therefore I would like to discuss this, before really going out and filing an issue (possibly wrongly). you can submit an issue for the docu if you want Juergen Any comments/hints/insights? ---rony - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Re: [qa-dev] Re: [dev] proposal for change of cws policies
Hi, good work, but I miss the point where it is mentioned that there must be a link to the installsets for the QA. This should not be a nice to have but a must, otherwise the QA representative has to ask the cws owner for the installsets (with the delay which maybe occurs because of different timezones etc.) or find someone who can build the installsets locally. Greetings, Oliver Eike Rathke wrote: Hi Martin, On Wednesday, 2007-07-04 17:04:39 +0200, Martin Hollmichel wrote: modified version of the child workspace policies on http://wiki.services.openoffice.org/wiki/CWS_Policies http://wiki.services.openoffice.org/wiki/CWS_Policies#Build_Configurations | A CWS must be built on at least two platforms in the product version | (Windows and one UNIX platform) How will we ensure that non-Hamburg based CWSs can be built on these platforms and install sets be made available? The main difference compared with the old policies are * How to group task goes now much more in detail to make more clear in which cases what people are needed to review the work on a child workspace. * added more links to documentation on how to approve a CWS * removed superfluous wording and sentences. Nice work. I suggest that we make this cws policies official on July 11th if there are no objections until then. +1 (given that the platform obstacle will be sorted out or handled relaxed) I think some sections need to be checked against / merged with / link to sections of http://wiki.services.openoffice.org/wiki/CWS which in some aspects is more detailed, and in other aspects should be replaced with the new policy. If these changes get accepted I propose to exchange the Level of impact in the EIS application accordingly to the new categorization of cws in the policies. +1 Eike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Bug in determining Java type for UNO_LONG properties ?
Hi Jürgen, Problem: using a property's' Type attribute (prop.Type) one works with a com.sun.star.uno.Type object (cf. http://api.openoffice.org/docs/java/ref/com/sun/star/uno/Type.html) it seems that for UNO_LONG types (prop.Type.getTypeClass() returns an UNO_LONG TypeClass object), whereas prop.Type.getTypeName returns the string name long instead of int. you get always the UNO type name and not the mapped name for a specific language binding. Thank you very much for this clarification! The documentation of com.sun.star.uno.Type is not totally clear for me, therefore I would like to discuss this, before really going out and filing an issue (possibly wrongly). you can submit an issue for the docu if you want Hmm, maybe this is not warranted (saving resources for other issues). ---rony - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] RE:[dev] question about use XStorag
Hi, On Friday, 2007-07-06 09:20:57 +0200, Rüdiger Timm wrote: is based on the source of OOB680 . Why do you have to use such an old code base? I'd strongly recommend to update to f.e. OOF680 m18, the latest release. From my point of view it does not make sense to do development based on old code. In terms of development I'd even consider the OOF680 branch as way old and patches don't necessarily apply on SRC680 anymore. I'd recommend a recent SRC680 milestone instead, currently the latest available being SRC680_m219. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to this [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Use [EMAIL PROTECTED] Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] RE:[dev] question about use XStorag
Eike Rathke wrote: Hi, On Friday, 2007-07-06 09:20:57 +0200, Rüdiger Timm wrote: is based on the source of OOB680 . Why do you have to use such an old code base? I'd strongly recommend to update to f.e. OOF680 m18, the latest release. From my point of view it does not make sense to do development based on old code. In terms of development I'd even consider the OOF680 branch as way old and patches don't necessarily apply on SRC680 anymore. I'd recommend a recent SRC680 milestone instead, currently the latest available being SRC680_m219. That depends. If you are developing an extension that should run on the current stable release it's not a bad idea to use this code line for development. But using OOB680 is definitely not recommended. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] RE:[dev] question about use XStorag
chensuchun wrote: Sorry, there is no OwnSubFilter service in my openoffice, my openoffice is based on the source of OOB680 . As recommended by others: you should upgrade. I want to try an other way. My idea is as following: 1. use loadComponentFromURLto open the document in hidden mode. 2. copy the whole content and style from the XComponent returned fronm loadComponentFromURL to the mxDesDoc which is set by setTargetDocument. 3. close the hidden document. Can I do in the filter in this way? No, you can't copy the document content that way. If loadFromStorage() doesn't work you have to update and use the SubFilter. Perhaps you tell us what loadFromStorage() does. Or you can debug the code to see what goes on there. Maybe it's a bug in the code. But even then you had to update as nobody will fix bugs on this ancient code line. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Re: [qa-dev] Re: [dev] proposal for change of cws policies
Hi Oliver, On Fri, 2007-07-06 at 10:07 +0200, Oliver Craemer - Sun Germany - ham02 - Hamburg wrote: Hi, good work, but I miss the point where it is mentioned that there must be a link to the installsets for the QA. This should not be a nice to have but a must, otherwise the QA representative has to ask the cws owner for the installsets (with the delay which maybe occurs because of different timezones etc.) or find someone who can build the installsets locally. This, IMHO, is a little overkill for those who work outside of Hamburg. For instance, if the QA rep is located in Hamburg, and the developer is located remotely in his own home (like myself), there are several hurdles that need to be overcome. 1) Broadband connection, especially the uplink speed. Most residential ADSL has a very limited uplink speed, and it's designed such that, when the uplink bandwidth is fully utilized, the download bandwidth becomes close to nill. This means that, when he's uploading the installation set, or someone is downloading them from a server located from his location, his net connection is effectively down, which affects his other business. 2) Server availability to upload the installation set(s). This may not be a problem for those who work within a large organization. But for a single community member from his/her own home, this can be a huge overhead. I understand that many OO.o community members are devoted enough to take care of it themselves, but we should still not take their service granted. 3) Last, but not least, if the cws in question affects only a small part of the OO.o codebase (e.g. one small-ish patch), why make this process this heavyweight? If the issue involves only one or two patches for one or two modules based on an existing milestone (e.g. SRC680_m218), it should be easy to re-use an existing build to create installation set. If we have an automated buildbot that provides an installation set, it's a different story, though. Just my 2 cents. Kohei - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Re: [qa-dev] Re: [dev] proposal for change of cws policies
Kohei Yoshida [EMAIL PROTECTED] writes: If we have an automated buildbot that provides an installation set, it's a different story, though. There's supposed to be buildbots for said platforms - number and speed of those can clearly be improved upon, though. We've had intermittent trouble with the upload feature of some buildbots, so I'm not 100% satisfied with that yet. Main issue I have with this is that the buildbots (and tinderbox as well, BTW) are part-time projects of some volunteers, so this is not (yet) part of the official infrastructure. There'll be an improved buildbot system presented at OOoCon07, and I'd hope to see a bit more interest sparked, then... Cheers, -- Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] [api-dev] Debugging on Linux with remote access
Hi Eike, Hi Björn, On Thursday, 2007-06-28 08:55:49 +0200, Björn Milcke wrote: 1. Start StarOffice like this in a shell: [...] 2. I start gdb this way: gdb soffice.bin PID of soffice.bin [... set breakpoints ...] = The office freezes, gdb no longer reacts, the API test does nothing. Just by chance, did you start the gdb 6.3 from within the setsolar unxlngi6 baseline environment? I once had a similar experience and using the local machine's gdb 6.5 without a setsolar environment solved the problem. Please draw Hamburg RE's attention to this problem, sorry for not having done so earlier. I just tried gdb 6.6, and it worked well, but the issue is already fixed, so I have no direct comparison. ;-) Well, seems to be an improvement, anyway. Would make sense to have this in the environment rather than a broken gdb. -Bjoern - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
