Re: Triage for AOO 4.0.0 Release Blockers
On 6/20/13 8:01 PM, Edwin Sharp wrote: > Yes. > please allow to share the following objections: > 1. in general, bugs shouldn't be rated I disagree here and you always rate issues starting with setting a priority. And as always you can't fix them all with a fix number of developers. It simply doesn't work. That means you have to prioritize and that is quite normal. > 2. most are crashes - "release blocker" can be other than crash - i.e. copy > chart from Calc into Writer results in chart area without curve. this is a > huge bug that doesn't involve a crash exactly and we have defined some criteria for issues, crashes, data loss and security issues have always high priority. Regressions are also very important especially when often used functionality is broken. It is documented in the wiki but I haven't the reference in place yet, have to look for it. > 3. with all the respect to Norwegian users, print dialog too wide is a > negligible problem not for this specific user group and the fix is already available. > 4. there should be a documented evidence to the bug evaluation process, based > on approved SOP I am not sure if I understand you here > 5. the general public has no declared release date - no need to rush as there > is no commitment to fulfill no but the project have committed to a release date and I believe the majority of the community support the new release. You have to set a date and have define what is important for this date. You can always do more and can fix more issues but that won't work very well. > 6. "minor" bugs should also get attention and be targeted definitely but not short in front of a release. And of course nobody prevent anybody from fixing such issues. We have a lot of them, many are probably not longer valid and can be closed, other are not easy to fix and so on. A good start would be of course to simply check older issues if they are still valid or not. > 7. the judgment of introducing the sidebar with so many pending bugs should > be justified to demonstrate openness as far as I know we haven't pending bugs here. Don't mix this up with improvement or feature requests. Maybe I don't understand you and you can explain it again > 8. RTF is rarely used today - no reason for two appearances in the list RTF is as far as I known relevant for Ms interoperability in general and important for other MS filters as well. Even the pure format is not used often the functionality is important. If somebody knows more please correct me. > 9. Are there no "critical" bugs in Math, Draw and Base? probably yes and probably many other critical bugs in other areas that are not detected yet or not proposed as showstopper > 10. Are there enough volunteers to treat these "release blockers" on time? we hope we can fix them all but volunteers are never enough ;-) If you think that other issue should be showstopper as well, please propose them on the dev list and we can discuss them. That's the way how we want to handle it Further discussion should take place on the dev list Juergen > Thank you > > > > On Thu, Jun 20, 2013, at 18:09, Oliver-Rainer Wittmann wrote: >> Hi, >> Any objections to mark these issues as release blocker? >> >> [1] >> https://issues.apache.org/ooo/buglist.cgi?quicksearch=120250%20120443%20120513%20120559%20121008%20121143%20121256%20121435%20121479%20121751%20121925%20121968%20121977%20122163%20122300%20121772&list_id=68303 >> >> >> Best regards, Oliver. >> >> - >> To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: qa-h...@openoffice.apache.org >> > > - > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org > For additional commands, e-mail: qa-h...@openoffice.apache.org > - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Regarding test case 1405 (impress)
Hi , Prachi I think it should add special description for textbox ,like what you mention above: textbox default fill type is 'None' and not a bug for AOO But because the testcase had frozen by testing cycle ,i will modify this test case later if no arguement Thanks your questions and effort On Fri, Jun 21, 2013 at 8:02 AM, Prachi Jain wrote: > > In test case 1405 > http://aootesting.adfinis-sygroup.org/lib/testcases/archiveData.php?edit=testcase&id=17863 > Step no 3 says in area section in sidebar "Default Fill type is 'Color > (default color)' when textbox inserted into presentation" > > But while executing step 3 for textbox Default fill type is 'None'. Is it > a bug ? or "Default Fill type is Color" only applies to drawing object and > fontwork. > > Thanks > Prachi
Regarding test case 1405 (impress)
In test case 1405 http://aootesting.adfinis-sygroup.org/lib/testcases/archiveData.php?edit=testcase&id=17863 Step no 3 says in area section in sidebar "Default Fill type is 'Color (default color)' when textbox inserted into presentation" But while executing step 3 for textbox Default fill type is 'None'. Is it a bug ? or "Default Fill type is Color" only applies to drawing object and fontwork. Thanks Prachi
Re: Triage for AOO 4.0.0 Release Blockers
Yes. please allow to share the following objections: 1. in general, bugs shouldn't be rated 2. most are crashes - "release blocker" can be other than crash - i.e. copy chart from Calc into Writer results in chart area without curve. this is a huge bug that doesn't involve a crash 3. with all the respect to Norwegian users, print dialog too wide is a negligible problem 4. there should be a documented evidence to the bug evaluation process, based on approved SOP 5. the general public has no declared release date - no need to rush as there is no commitment to fulfill 6. "minor" bugs should also get attention and be targeted 7. the judgment of introducing the sidebar with so many pending bugs should be justified to demonstrate openness 8. RTF is rarely used today - no reason for two appearances in the list 9. Are there no "critical" bugs in Math, Draw and Base? 10. Are there enough volunteers to treat these "release blockers" on time? Thank you On Thu, Jun 20, 2013, at 18:09, Oliver-Rainer Wittmann wrote: > Hi, > Any objections to mark these issues as release blocker? > > [1] > https://issues.apache.org/ooo/buglist.cgi?quicksearch=120250%20120443%20120513%20120559%20121008%20121143%20121256%20121435%20121479%20121751%20121925%20121968%20121977%20122163%20122300%20121772&list_id=68303 > > > Best regards, Oliver. > > - > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org > For additional commands, e-mail: qa-h...@openoffice.apache.org > - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Triage for AOO 4.0.0 Release Blockers
Hi, On 06.06.2013 13:54, Yuzhen Fan wrote: Hi All, Here is the list of identified candidates[1]/[2] which are proposed to be 4.0.0 release blockers. Please indicate your selections for release blockers by giving 1 vote to 1 bug (the vote field is beside the importance field, in a bug form). We hope to get the vote score this week, any bugs you think most critical to you, please bring out and let's discuss. [1] https://issues.apache.org/ooo/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=4.0.0_release_blocker%3F&sharer_id=249289&list_id=64740 [2] Also attach the file for the list (AOO4.0.0_release_blocker_candidates.ods) Armin, Jürgen, Andre and myself reviewed in the last days the list of issues which had been requested for release blocker (release blocker flag = '?') and are not solved. We propose the following issues as release blockers [1]: - 120250 - 120443 (actually 121772 - 120443 is a dup. of this one) - 120513 - 120559 - 121008 - 121143 - 121256 - 121435 - 121479 - 121751 - 121925 - 121968 - 121977 - 122163 - 122300 Any objections to mark these issues as release blocker? [1] https://issues.apache.org/ooo/buglist.cgi?quicksearch=120250%20120443%20120513%20120559%20121008%20121143%20121256%20121435%20121479%20121751%20121925%20121968%20121977%20122163%20122300%20121772&list_id=68303 Best regards, Oliver. - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Call for volunteers to do exploration test on Base / Drawing and write test cases for Base / Drawing:
Hi All, This is call for volunteers to do exploration test on Base / Drawing and write test cases for Base / Drawing: 1. About exploration test on Base and Drawing, please could volunteers report in QA mail group on (1) covered platform/build/database; (2) tested scenario/steps; (3) test result/defect found, by updating these two web links: http://wiki.openoffice.org/wiki/QA/AOO40_Database for Base, and http://wiki.openoffice.org/wiki/QA/AOO40_Drawing for Drawing. Reference: Base test matrix http://wiki.openoffice.org/wiki/QA/Tescase 2. About writing test cases for Base, I have completed to create hierarchies of test suites in TestLink based on the finalized test matrix http://wiki.openoffice.org/wiki/QA/Tescase. Please could volunteers navigate the test suite tree view in the Test Specification (Test Project is Apache OpenOffice testproject), and let's following below process to organize test case writing: 1) Volunteers provide their TestLink ID and list of their preferred test suites to Yu Zhen Fan (fanyuz...@gmail.com) (Currently I have Anil Kumar's TestLink ID and confirmation to write test cases) 2) Yu Zhen specifies the test suites' assignment to the individual volunteer 3) Volunteers write test cases in the assigned test suites, in TestLink. For test cases related to connectivity testing, please attach the "live" test DB(s) and provide steps to set up test environment in "Preconditions". It's encouraged test cases' author to test his/her test cases in execution stage. 3. I will work with Liu Ping Tan on test matrix for Drawing later this week, if you have interest on Drawing test case writing, please let me know, I will put you in the pipeline. Regards, Yu Zhen
