Hello Caio, It seems you misunderstand me. Okay. I'll explain a bit more.
From: Caio Tiago Oliveira <[EMAIL PROTECTED]> Subject: Re: [qa-dev] Automated GUI Testing: What is a 'global' CWS and how do we test it? Date: Sat, 17 Mar 2007 16:04:32 -0300 > I meant: how to integrate the QA on Mac OS X with some non-Mac related > CWS's. > If someone is touching a file with Mac specific code and modifying the > non-Mac specific part, he could break it on Mac and don't notice. Yes. This is the main problem. Practically, but after the integration, we can submit patches and can integrate after a few milestones, having discussion with Ono-san. Is it a really big issue? I'm not talking about RC process. Hamburg QA team has done QA of global CWS for all platforms; GNU/Linux, Solaris, and Windows. mingwport03 cws is a global CWS. However, MacOSX build was broken. IMHO, implementing as policy for including build ability for other platform is not good for ordinal development cycle (not RC) CWS nomination process. Because: 1. CWS nomination process. Hamburg team should handle CWS nomination process. I don't think others can handle. They are not only doing buildablity check for GNU/Linux/Windows(4nt)/Solaris but also doing QA. (this is what Jogi wrote before) It is very very tough job. I understand why Hamburg QA/RE team only do QA for specific platforms. Their resouces are also severely limited. We sometimes need patches for SRC680_m* as well. this is called master fix. See below. (Still enviromnet is bit different from outside of Hamburg, they do not use configure) 2. VCL testtool problem. Assume MacOSX team's resouce is rich enough to do every CWS QA. VCLtesttool script is not solid for outside of Hamburg team. Can you reduce the number of errors to zero? No. See also, Andre's issue http://www.openoffice.org/issues/show_bug.cgi?id=74868 . (That's why I'm interested in this tool too.) 3. There are also practical way of doing things; raise as issues to keep it buildable. Problem here is mingwport03 cws breaks other ports. This is unfortunate for such a big cws. Raise as issue with patch for mingwport03 is a practical way of fixing issues. We need good communication, too. I think, we should not talk at #i53572#. If it is integrated, small patches may still needed for other platforms, but I think MacOSX team is active enough to create/integrate patches very soon. Do we have to keep buildable for every milestone striclty without patches? I don't think so. Even for GNU/Linux, there are some milestones that need pathces for outside of Hamburg team. If fixes are trivial, we fix them as master fixes. http://www.openoffice.org/servlets/ReadMsg?listName=releases&msgNo=8529 > I was talking here mainly about QA on CWS's (of course the test on the > RC's is still very important). > Buildbots are doing some kind of QA on CWS's for Mac, but it's only > about the build process. This is not sufficient. You need to submit patches as well. These patches must be buildable for all platforms(!). Also discussion with Ono-san is also very important. Of course, situation will change if this some cws is included in the RC process for mature ports. For such a case, this is a showstopper. Martin will take care of it. (BTW: if configure is broken, it won't be a showstopper. Such case is 2.0.2. see http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=9462 and #i62535# and even though, if there are other showstoppers, this might be included) I have such kind of problems too, for FreeBSD. Just raise as an issue, creating patches, and integrate them. My stand points are: a. Not expect perfect for development cycle. it exhausts developers/resources. b. our resources are limited and we expect outputs are maximum ;) c. there are practical way of keeping buildability. d. I'm not talking about RC process. e. there are not so many unfortunate CWS like mingport03. If so many, we expect even stability and we cannot do porting! Questions are very welcome. All the best, -- Nakata Maho ([EMAIL PROTECTED]) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
