Hi Mox Mox Soini schrieb: > While I agree that 3 months is a tight schedule for all the quality > checking > work etc, I think there would be very big danger of slowing down the > development and lower quality of the products, if the release schedule > would > be longer than 3 months. > ... > Longer development cycles are just not acceptable. If QA time is more > than 1 > month, there will be lot's of new code in the non-stable development > branch, > that will get bad quality, because everyone is concentrating in QA:ing the > stable release. So after the release is done, then there will already be a > bad quality development release to work with.
OK; I see your point. But you just gave the second best answer. The point so far is: QA (at least Mac QA) is not longer able to test all these funny new things all these engaged programmers write. So we can not keep up the pace the project goes. So, what we will get by your proposal is a three class "society": First class: Windows & Linux - QAing every release, making the pace; 2nd class will be Mac & ??, leaving out every second release and 3rd class would be more seldom OSses with just one release every year or so. But the better way would be (at least imho) that we think about another approach: *Less coding - more QA* . Reads: Putting less resources in coding and more resources in QA. OK, QA is not such a funny thing as coding. But it's surely the better way to a high quality product. Perhaps the project should even do more reengineering (I know, that's an even worse job than doing QA). I remember a mail on [EMAIL PROTECTED] "Thoughts about a world without VCL" (http://porting.openoffice.org/servlets/ReadMsg?listName=mac&msgNo=3277). Very good argumentation by Christian Lippka. But still the coding of new features goes on and on (in germany, we call that "featuritis" - like an illness). An QA s not keeping pace. And necessary re-engineering stays a hazy vision. Me personally can live happily until the end of my days with "slowing down the development" as you wrote. I agree so far that the pace of writing new code is and must be the pace of the whole project - but my answer is to slow down exactly this and use the then free resources on other places where they are needed urgently. This is nor necessarily QAing Mac-X11-builds - not even Vietnamese ones ;-) But this kind of slowing down would also do good help to them. -- Mit freundlichen Grüßen Uwe Altmann Ansprechpartner des deutschen Projektes für OpenOffice.org auf dem Mac http:/de.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
