Tracking bugs like Issue 124985 - [Meta] Meta Bug for collecting bugs which appeal for AOO 4.1.x
Hi, my experience is that such tracking bugs are not useful. The time invested in adding dependencies (what is rather uncertain, who can know how many bugs are missing and on what facts the various contributors added the bugs to the Meta) should be invested (with much more benefit) into careful review of the related BZ bugs and completion of information in the BZ bugs. An example: Issue 124891 - CRASH when close sidebar with Navigator active https://issues.apache.org/ooo/show_bug.cgi?id=124891 I found that one with importance Normal, what is rather inappropriate, that one has blocker quality. Such a report should get an appropriate importance rating, that's enough. If all info in the reports is up to date a simple query replaces the Meta Bug. And why is Issue 124947 - Fullscreen Filter Freeze blocking the meta bug? Currently we know nothing, it's unconfirmed ... Issue 114361 - Read Error with embedded images after saving in Writer appeared with 3.2, why is this listed in a 4.1 related tracking bug? And so on. I recommend not to create tracking bugs what can be replaced easily by queries and if there is no evidence that they are necessary for the bug fixing process. And if there is a decision that the tracking bug should be created please follow Best regards Rainer Hyperlinks: [1] https://issues.apache.org/ooo/buglist.cgi?bug_severity=blockerbug_severity=criticalbug_severity=majorbug_status=UNCONFIRMEDbug_status=CONFIRMEDbug_status=ACCEPTEDbug_status=REOPENEDf3=OPf4=versionf5=versionf6=CPf8=cf_bug_typej3=ORlist_id=149754o4=regexpo5=regexpo8=equalspriority=P1priority=P2query_format=advancedv4=^4.1v5=^4.2v8=DEFECT - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Tracking bugs like Issue 124985 - [Meta] Meta Bug for collecting bugs which appeal for AOO 4.1.x
Hi Herbert, I think we have some misunderstanding here. It's an essential that information should be consistent at any place for Bugzilla. Here an overview concerning priority /severity of the issues listed in the meta-issue; ! Critical major normaltrivial ! Total ---!-!-- P1 !1 . . . ! 1 P2 !. . . 1 ! 1 P3 !. 4 5 . ! 9 ---!-!-- Tot!1 4 5 1 ! 11 So my question is why Issue 114361 with severity trivial has been considered by godlike decision (there is no reasoning, neither in Issue 124985 nor in Issue 114361) so serious that it has been added added to the meta bug? With some minimum carefulness the severity would have been rised to major or more, the dataloss keyword would have been added, so that the decision will be comprehensible. I did that now in Issue 114361 Common known characteristics of unresolved Issue 124985 blocking Bug reports you find in Report [1] (More than 3400). So the question is why have 11 been picked as blocker for the meta issue, but more of 3400 not [2]? With some minimum corrections for the criteria of possible Meta bug blockers I can reduce the number by 90% [3] [4] Sorts these issues by priority /severity, the 12 with critical + P2 need some urgent review as I did for Issue 118725 - images dropped by random https://issues.apache.org/ooo/show_bug.cgi?id=118725 Issue 122780 https://issues.apache.org/ooo/show_bug.cgi?id=122780 and others And so on. Such systematic working is the only way for real progress. If after some work we have valid data in the bug reports Meta Bugs indeed can be useful to show up dependencies and relations what are not simply visible in the bug reports. For anything else queries like https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamedlist_id=149854namedcmd=Potential411Blockers (shared with registered users) are much more powerful, especially in projects with bigger community than AOO and much bug tracker activity (20 reports per day, not only 2). Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Please disable 4.1.0 Update Info!
Hi, I submitted Issue 124913 - Disable 4.1.0 Update Info https://issues.apache.org/ooo/show_bug.cgi?id=124913 because I think that it would be irresponsible to encourage users to update to 4.1.0 with known issue. I also think that there should be a hint in 4.1.0 Release Notes under Known issues CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Please Review 4.1 Release Notes
Rob Weir schrieb: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes Hi, has there been any progress concerning spell check problem http://www.openoffice.org/development/releases/3.4.1.html#AOO3.4.1ReleaseNotes-KnownIssues? If not, I think we should mention that issue. CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: propose AOO 4.1.0 RC - Showstoppers?
Hi, we have a potential showstopper Issue 124607 - .odt with (Page-No) field in header/footer and comment for text range fails to open with Read Error. Error reading file https://issues.apache.org/ooo/show_bug.cgi?id=124607 CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Wrong regression test cases
Hi, from time to time there is a suspect that there are errors in test case descriptions, currently I know: Issue 124523 - Testcase requires not existing feature wildcards https://issues.apache.org/ooo/show_bug.cgi?id=124523 Issue 124535 - Wrong Test description for hyperlinks in Writer TOC https://issues.apache.org/ooo/show_bug.cgi?id=124535 Is there any systematic review for the testcases? How should we proceed if errors have been found? CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
New Bug reporters March 2014
Hi, in March 2014 we have got 47 new AOO Bug reporters, who reported all together 55 bugs: No Reports Account --- 04anu6j...@gmail.com 03karlo.s...@gmail.com 02j.nitsc...@ok.de 02overcomer@gmail.com 02shlap...@henrico.k12.va.us 0173wa4...@sc.rr.com 01aeneum...@gmx.net 01agnies...@unity3d.com 01alexander.re...@googlemail.com 01alwynwelling...@gmail.com 01a...@luycx.com 01bobti...@earthlink.net 01bugzillaopen...@gmail.com 01claircou...@yahoo.co.uk 01daveun...@sbcglobal.net 01djpi...@hotmail.com 01edkni...@centurytel.net 01elke.dou...@free.fr 01galearn...@gmail.com 01gregpe...@hotmail.com 01gus.h...@gmail.com 01gwmcc...@charter.net 01halst...@gmail.com 01jak.badd...@hotmail.com 01kg.hammarl...@gmail.com 01lawall...@gmail.com 01leonb...@gmail.com 01lu...@crossimp.com 01lughnas...@seznam.cz 01majella.paul...@gmail.com 01marih...@qq.com 01maryfai...@hotmail.com 01mcleo...@gmail.com 01openoff...@margull.de 01p.jungw...@gmx.net 01paulp...@optonline.net 01pbd62...@icloud.com 01philip.mar...@outlook.com 01sandra.il...@yahoo.com 01szurketest...@gmail.com 01t_p_ander...@hotmail.com 01thesim...@gmail.com 01tio.mad...@hotmail.com 01turner_jm...@live.com 01voro...@gmail.com 01wegwe...@gmx.de 01wojciech.halicki.pis...@gmail.com Thank you all for your initiative. If you have any questions concerning your Bugzilla bug reports please feel free to add me to CC in the bug report. Best Regards Rainer Bielefeld - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Reminder: [Issue 124572] New: Edits blocked with message: Your IP address has been automatically blocked
Hi, seems our Wiki is damaged. AOO area or Apache Infra? CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Specifications for Enhancement Requests
Hi all, today I read [Issue 124455] introducing a attribute for spacing between paragraphs with the same paragraph style https://issues.apache.org/ooo/show_bug.cgi?id=124455. I think it's an Idea what is worth to think over, but it is one of those where several relations and possible obstacles have to be considered before a decision can be done whether we want to invest developer time for implementation. I think for complex requests we should create something like a short specification where we collect all facts and thoughts, try to reach common sense how we should proceed. https://wiki.openoffice.org/wiki/Specification_template seems a little oversized, too complex and so rather deterring. Does anybody know a more simple Template, more or less similar to a check-list for the essentials like * possible benefit * risks * To be considered, related issues * alternatives (different solution, Extension) * real life scenarios * competitors' approach * accessibility impact, * Related Bugzilla issues CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Wework Wiki: Test Case Management
Hi, https://wiki.openoffice.org/wiki/Test_Case_Management Needs some rework before we can add a Link to Bugzilla Component. I am not familiar with that stuff. Best Regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Fwd: Update Available: Apache OpenOffice
Hi, few minutes ago I got following reminder 2 times. They are a little late for 4.0.1? Any Ideas? The Download Latest Version link leads to nirvana. CU Rainer Original-Nachricht Betreff:Update Available: Apache OpenOffice Datum: Thu, 27 Mar 2014 16:42:10 + Von:SourceForge.net noreply-upda...@sourceforge.net An: rainerbielefeld_ooo...@bielefeldundbuss.de Update Available: Apache OpenOffice SourceForge http://sourceforge.net *Find*, *Create*, *Publish* Open Source Software for *free*. Hi! You have an update available. Apache OpenOffice http://sourceforge.net/projects/openofficeorg.mirror/ Apache OpenOffice http://sourceforge.net/projects/openofficeorg.mirror/ Apache OpenOffice, the Free and Open Source Productivity Suite Apache_OpenOffice_4.0.1_Win_x86_install_en-US.exe Released on 2013-09-25 DownloadLatest Version http://sourceforge.net/projects/openofficeorg.mirror/files/latest/download?utm_campaign=updaterutm_medium=emailutm_source=subscribers Unsubscribe http://sourceforge.net/projects/openofficeorg.mirror/unsubscribe?email=rainerbielefeld_ooo...@bielefeldundbuss.de me from receiving notifications for this project. This e-mail was intended for: rainerbielefeld_ooo...@bielefeldundbuss.de mailto:rainerbielefeld_ooo...@bielefeldundbuss.de Unsubscribe from project http://sourceforge.net/projects/openofficeorg.mirror/unsubscribe?email=rainerbielefeld_ooo...@bielefeldundbuss.de | Manage your subscriptions http://sourceforge.net/user/updates?email_hash=7bdc50a5de9ab3c89321c555036db8c4 | Privacy policy http://slashdotmedia.com/privacy-statement/ SF http://sourceforge.net - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
German authorities want to improve AOO - LibO
Hi, is someone from Germany observing this? http://www.heise.de/open/meldung/Behoerden-wollen-Libre-OpenOffice-verbessern-2152858.html Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
AOO Bugzilla
seems to be down? Best regards Rainer Bielefeld - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO Bugzilla
Hi, worked for few minutes, now again Error: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /ooo/report.cgi. Reason: Error reading from remote server Might be coincidence? 2 times stopped working after I starte a reporrt-query https://issues.apache.org/ooo/report.cgi?x_axis_field=reporter_realnamey_axis_field=reporterz_axis_field=no_redirect=1query_format=report-tableshort_desc_type=allwordssubstrshort_desc=longdesc_type=allwordssubstrlongdesc=bug_file_loc_type=allwordssubstrbug_file_loc=keywords_type=allwordskeywords=bug_id=bug_id_type=anyexactvotes=votes_type=greaterthaneqemailtype1=substringemail1=%40emailassigned_to2=1emailreporter2=1emailqa_contact2=1emailcc2=1emailtype2=substringemail2=emaillongdesc3=1emailtype3=substringemail3=chfield=[Bug+creation]chfieldvalue=chfieldfrom=2000-01-01chfieldto=2014-02-28j_top=ANDf1=noopo1=noopv1=format=tableaction=wrap CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.1. Regressions
Yuzhen Fan schrieb: Here is the analysis of possible cases Hi, plausible description of the task, I'm more or less proceeding so. I will send you bug list for your review Difficult - I currently prefer to check issues where I have knowledge first, not to proceed a list. Other volunteers might think similar. If you agree we can use my https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamedlist_id=133742namedcmd=410_RegressionTest (or something similar?) for a while, I can add Exclude issue numbers what have been checked and are no regressions after short mail here, rest fall out of the list one by one because they got keyword regression or more early version number or whatever. Nevertheless, we should find proceedings what can increase efficiency by avoiding double work. May be some volunteers add themselves to QA Contact in bugs where they have skills and want to proceed them within a week or so? CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.1. Regressions
Hi, and we need help of an an experienced MAC user for [1], it seems we have some MAC-Only issues in the list. CU Rainer Hyperlinks: [1] https://issues.apache.org/ooo/buglist.cgi?bug_severity=blockerbug_severity=criticalbug_severity=majorbug_severity=normalbug_status=UNCONFIRMEDbug_status=CONFIRMEDbug_status=ACCEPTEDbug_status=REOPENEDf1=keywordsf2=bug_idf3=cf_bug_typef4=op_sysknown_name=410_RegressionTestlist_id=133748o1=notsubstringo2=nowordso3=equalso4=regexpquery_based_on=410_RegressionTestquery_format=advancedresolution=---v1=regressionv2=1000%20124211v3=DEFECTv4=^Mversion=4.1.0-dev - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.1. Regressions
how about the defects already have value in QA Contact Hi, https://issues.apache.org/ooo/buglist.cgi?cmdtype=doremlist_id=133813namedcmd=410_RegressionTest_woQAremaction=runsharer_id=8583 Shows the possible regressions without someone in QA, only 5 found. Not many left ... Let's wait until 80 % of the big list have been proceeded, then we can care about refining that ;-) CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Beta Survey
Rob Weir schrieb: 1) What platform they ran with PC 2) What language they used German WIN, German, French, Wpanish, EN-US UI and Localization for tests 3) How many hours they have used AOO beta 1 hour per day or so 4) Which apps did they use Writer, Calc, Draw 5) What file formats did they read/write Mainly ODF 6) Link to a list of P1 bugs reported on beta: Did they encounter any of these bugs? No 7) Did they encounter any other bugs? (Nudge them to enter a BZ report) I did not find own new bugs with 4.1.0 Beta 8) Did they try any of the new features in AOO 4.1 (list them) Can't remember, don't think so 9) Any other comments (free text response) Regression situation with 4.1.0 still rather unclear, see my posting 4.1. Regressions Rainer Bielefeld - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOOTest-277
Rainer Bielefeld schrieb: can someone please check whether test descriptions for above mentioned test are correct? Thanks to Sandhya Sivakumar, who left a comment in the Bug. CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.1. Regressions
Hi, I think Bugzilla Help https://issues.apache.org/ooo/describekeywords.cgi tells it all. There only is no common sense whether key word should be used also for very old regressions (regression in OOo 1.0.1 compared to OOo 1.0.0), from developer's point of view only regressions in AOO 3.4-dev and later are of interest. https://www.mail-archive.com/qa@openoffice.apache.org/msg01787.html Generally problems with newly integrated features can not be regressions. But if the code of a newly integrated feature damages an older function so that it does not work correctly since integration, that damage deserves key word regression. But I do not think that many regression key words will have to be added. The problem with the Bugs in the list is that at least one of following mistakes is in data for the Bugs: * Version has been changed to 4.1 in error, example: (Bug 105492 - Text Orientation Degrees Entry Field * It has not been tested with what Version the bug has appeared, example: (Bug 124259 - mathvariant=normal is ignored on import of .mml file) So far my personal thoughts, what are result of long co-working in open source projects, CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1. Regressions
Hi all, last weekend I wanted to check whether I can try to use 4.1 for my daily work with acceptable risk. Using such a trunk version for normal work is a much more manifold and reliable test than testing with prepared testcases (what, of course, have to be done, too!). I am used to do a query for regressions in trunk, what will allow to check whether there are known 4.1 regressions affecting my daily work. And fascinating, my query showed 1 Regression in 200 Bugs with Version 4.1 (I forgot what one it was). That sounds good, but it is completely implausible that our 200 unfixed 4.1.0-dev DEFECT bugs all are about new features. And that tells that information in Bugzilla database is totally unreliable, not useful for such decisions. I already started a review of Bugs in query [1]. Very often Version has been changed erroneous from an older version to 4.1, sometimes additionally I see reports with Status Confirmed what are no bugs at all (Bug 106106, Bug 97818), or at least are very unclear (Bug 96263. May be some volunteers can assist? Best regards Rainer Hyperlinks: [1] https://issues.apache.org/ooo/buglist.cgi?cmdtype=doremlist_id=130944namedcmd=410_RegressionTestremaction=runsharer_id=8583 (shared with canconfirm) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: first Beta RC ... Bug 124272 - Error message Truetype error 2704 when install language pack on en_US snapshot
Hi, I still can't install Language packs because of https://issues.apache.org/ooo/show_bug.cgi?id=124272 CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bug 124114 - Auto Detection for mime type selects text/plain instead of application/vnd.oasis.opendocument.text - Reminder
Hi all, anything new here? Auto mime type recognition is really bad, not only writer.ods affected, see Bug 124293 - Section Range names truncated from underscore to end in MSO .XLSX https://issues.apache.org/ooo/show_bug.cgi?id=124293! Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Bug 124268 - OOXML import problems
Hi, I think we should decide whether we want to use a tracking bug [2] or a Key word (interop_OOXML) [2]. Using both in parallel only makes it more difficult to create reliable queries. CU Rainer Hyperlinks: [1] https://issues.apache.org/ooo/show_bug.cgi?id=124268 [2] https://issues.apache.org/ooo/buglist.cgi?keywords=interop_OOXML%2C%20keywords_type=allwordslist_id=126117query_format=advanced - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bug 124268 - OOXML import problems
Edwin Sharp schrieb: Keywords or Tags should be preferred. Hi, especially because availability is visible for everybody keyword selector, while Tracking bugs need expert knowledge that they do exist. Tracking bugs are favorable if there is no simple relation does exist (Blocks TrackingBug1, what itself depends on TrackingBug2 ... . Dependency trees are useful sometimes, but my experience is that for most issues a simple Tag like [sidebar] in the summary does the job. For my workflow the Tracking Bugs have few impact, but of course that might be different for other users. CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Wikis down
Hi all, Wikis have been down for 2 days or so, http://monitoring.apache.org/status/ shows critical for half the infrastructure, but latest news on Twitter is Feb 11: Great news for @theASF projects using GitHub! Sometimes miracles take a little longer, but (if no quick solution is foreseeable) shouldn't there be some info for the users of the infrastructure? And for the AOO users despairing of tons of not working Wiki-Links on https://www.openoffice.org/, especially documentation? I think the http://www.openoffice.org/ header (Apache OpenOffice The Free and Open Productivity Suite) should get a short hint like Our Wikis are temporarily down, please excuse us for inconvenience. CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wikis down
As a fast solution, I've updated the contact_us Hi, thank you, I should have asked yesterday, it always works that few minutes after such a measure the problem will be solved ;-) Indeed, wiki.openoffice.org is back again. But cwiki still seems to have problems? Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Bugzilla: User Sam Jennings
Hi all, may be someone feels able to explain to above mentioned user how to use Bugzilla in an appropriate way? Or wants to block user Sam Jenning's Bugzilla account samjenni...@hotmail.com for a week or so for educative reasons? He is engaged and may be even talented, but unfortunately he also ignores all guidelines and violates the bugfixing workflow with his back seat driver attitude as it can be seen in https://issues.apache.org/ooo/show_activity.cgi?id=124210 In private mails I tried to explain to him as polite as I can, but unfortunately I failed, as can be seen in Comment 11 of Bug 124210 and Comment 1 of Bug 124237. I will simply ignore all Bug reports where he is involved in future Best Regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Bug 124114 - Auto Detection for mime type selects text/plain instead of application/vnd.oasis.opendocument.text
Hi Infrastructure Team, first: Thanks a lot for fixing of Re: AOO [Bug 122235] Connection fails with 502 Error reading from remote server! Never again I have been bothered by downtimes since that fix. Now my new request: https://issues.apache.org/ooo/show_bug.cgi?id=124114 For a while it seemed that the problem had been solved by updating Bugzilla, but now problem has reappeared, it seems that (at least with my Seamonkey 2.2.4) Auto-Mimetyp-detection never finds the correct application/vnd.oasis.opendocument.text. Mostly result is text/plain, but sometimes also exotic application/3dr [1]. And I am not the only one who suffers from that problem [2]. I found some Bugs in BZ Bug Database [3], but none of them seems to be concerning this problem. Did we have a downgrade from BZ 4..4.2 (told in OOo dev mailinglist, I did not check) to BZ 4.4.1? Can you help? Best regards Rainer Bielefeld Used Hyperlinks: [1] https://issues.apache.org/ooo/buglist.cgi?f1=attachments.mimetypef2=attachments.filenamelist_id=124012o1=substringo2=substringquery_format=advancedv1=3drv2=odt [2] https://issues.apache.org/ooo/buglist.cgi?f1=attachments.mimetypef2=attachments.filenamef3=attachments.submitterlist_id=124013o1=substringo2=substringo3=notequalsquery_format=advancedv1=3drv2=odtv3=rainerbielefeld_ooo_qa%40bielefeldundbuss.de [3] https://bugzilla.mozilla.org/buglist.cgi?list_id=9398347short_desc=mime%20typeresolution=---resolution=DUPLICATEquery_format=advancedshort_desc_type=allwordssubstrproduct=Bugzilla - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Mentoring new Developers
Hi all, I know 2 charts, 1 with good news https://issues.apache.org/ooo/reports.cgi?product=-All-datasets=UNCONFIRMED and one with bad news: https://issues.apache.org/ooo/reports.cgi?product=-All-datasets=CONFIRMED I think we urgently need some assistance for the core developers by interested newbie developers Does AOO have a systematic approach how to interest new willing developers and to make sure that they have some sense of achievement when they start? And is that promoted at prominent places? Of course I know http://openoffice.apache.org/get-involved.html, but to me that all sounds bureaucratic and not very inviting. I think we (additionally) need an alternative approach, let's call it Easy Patches. My experience (as a not-developer, but engaged QA member) is that smaller UI-patches are a nice way to get some first experience with th code of the project; And mentoring for newbies does not cost too much time, a simple you find the code in xy area and a review of the patch should be enough in most cases. Examples for bugs what might need an easy patch might be these [1], I think there are a lot more. A part of this idea is to create a short introduction in the Wiki with an automatically generated list of such promising Easy Patch Bug reports, some developers willing to mentor and a very short instruction how to start some first steps to create a patch. Ideas, concerns, interest to support something like this? Best regards Rainer Used Hyperlinks: [1] https://issues.apache.org/ooo/buglist.cgi?bug_id=124200%2C124186%2C124054%2C124046%2C124012%2C120850%2C89934%2C124183%2C124119%2C124035%2C123931%2C122712list_id=123278 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Bugzilla: Keyword regression
Hi, currently the manual on https://issues.apache.org/ooo/describekeywords.cgi seems to suggest to use that keyword also for problems what appeared between OOo 1.0.2 and OOo 1.0.3. Such use might be correct as a matter of form, but I think useless for QA and developers daly work. regression key word indicates a major priority for fixing a bug, because appearance of new problems is bad for AOO's reputation. But a regression between OOo 1.0.0 and OOo 1.0.1 from 2001 (as an overstated example) is nothing what should cause major reputation loss for AOO in 2014. So I recommend to limit use of Keyword regression for all Problems what appeared with AOO 3.4-dev or later and to add a corresponding hint in Bugzilla Help. BTW: I recommend to keep those hints in Bugzilla short (not more than 2 text rows or so) and do link to more elaborated help in the Wiki (for example). Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bugzilla: Keyword regression
Rob Weir schrieb: I wonder whether a combination of the regression flag and the version field would give us everything we need to know? Hi, that's the main intentions behind my suggestion. If we know we have had a regression (not too long ago, with Regression keyword) and also have found the version where it appeared, we can find the commit what causes the problem. With reasons for the commit fresh in their mind developers should be able to fix that quickly. With old regressions that's more difficult, nobody remembers why the code changes have been done and what later commits' functions will break after changes in that area. So the regression keyword can be a flag showing that here is an annoying mishap what can be fixed with probably bearable costs. CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO [Bug 122235] Connection fails with 502 Error reading from remote server
Tony Stevenson schrieb: I will move the SQL DB that runs the AOO instance of BZ tomorrow morning Hi Tony, I already see the progress that Bugzilla is no longer blocked every morning. Is there anything left what might need some testing (may be Bugzilla access during a now shifted backup time or whatever else) or can we simply clos above mentioned Bug report? Best Regards Rainer Bielefeld - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO [Bug 122235] Connection fails with 502 Error reading from remote server
Tony Stevenson schrieb: Following the thread below, and the containing BZ issue in AOO space (and notably not in the Infra JIRA instance) - I will move the SQL DB that runs the AOO instance of BZ tomorrow morning at 07:30 (5 minutes before the currently scheduled backup that will ‘kill’ the service anyway.). Hi all, can someone please add a short announcement Bugzilla will be down for maintenance 2014-01-20 07:30 ... 08:30 UTC (estimated) on * https://wiki.openoffice.org/wiki/Main_Page (I would have done, but I do not have permissions) * http://openoffice.apache.org/get-involved.html and related localized pages * Bugzilla, may be in footer This is Apache OpenOffice (AOO) Bugzilla ... or so so that users will be informed? May be most QA staff users are used to that, but we should try to inform early normal users who might want to report a bug. Best Regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Unused patches
Hi all, we have lots of bug reports with unused patches. I think patches should be checked as soon as possible and be integrated as soon as possible. Example: I found 31 Bugs with unused patches by Kohei Yoshida - I think we can't get progress in Calc any cheaper. And also the other Bugs with unused patches should be checked ... BTW, I haven't a clue how to use custom search Attachment is a Patch. Can someone tell me? Best regards Rainer Hyperlinks [1] https://issues.apache.org/ooo/buglist.cgi?bug_status=UNCONFIRMEDbug_status=CONFIRMEDbug_status=ACCEPTEDbug_status=REOPENEDf1=attachments.submitterf2=attachments.ispatchlist_id=112364o1=equalsquery_format=advancedv1=kyoshida%40novell.com - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
BUGZILLA/FAQ
Hi, it would be great if some volunteers would help to replace the question marks on https://wiki.openoffice.org/wiki/BUGZILLA/FAQ by useful contents. Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: BUGZILLA/FAQ
Hi, thank you all for updating and completing the FAQ, I again learned some important details and I hope, information also will be useful for other users and help to unify information in the Bug reports. Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Bug 122235] Connection fails with 502 Error reading from remote server
Hi, waiting for Bugzilla becoming available again, I have some time for general meditations. Experience of life is that you should not confide your car to a garage where workers obviously are not interested in repairing their broken tools. May be during next BZ breakdown you find time to think about relation of this wisdom to the AOO project ... CU Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
AOO 4 unusable under Linux64?
Hi all, Edwin Sharp and some other users found several bugs [1] under Linux64, in summary the conclusion seems to be that AOO currently is more or less unusable with Linux 64. Can some developers please have a look? Best regards Rainer Used Hyperlinks: [1] https://issues.apache.org/ooo/buglist.cgi?chfield=[Bug%20creation]chfieldfrom=-360dchfieldto=Nowcolumnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Cversion%2Copendate%2Creporterf1=op_syslist_id=93343o1=substringop_sys=Linux64query_format=advancedresolution=---v1=linux - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Be Bugzilla (email) account seems broken, Bug 123259 - No mails from Bugzilla
Hi Rob, thank you for detailed info. I can't help with the core problem, but I have a general suggestion. I think it would be useful to have a thread at q...@openoffice.apache.org (or a similar appropriate mailing list) like this one I created at Libreoffice long ago: http://lists.freedesktop.org/archives/libreoffice-qa/2012-November/002976.html That thread is not for discussion, only for information by BZ admin(s) so that any interested affected staff has early information concerning changes in or problems with Bugzilla. Additionally such a thread is some kind of public log, what is useful for experts to interpret queries and similar activity. Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Be Bugzilla (email) account seems broken, Bug 123259 - No mails from Bugzilla
Hi, can someone please check and repair my BZ mail account? For details please see above mentioned Bug https://issues.apache.org/ooo/show_bug.cgi?id=123259 I additionally tried to modify my E-Mail-Adress, but I did not get a message, neither to old address nor to new one. As a makeshift I created a feed so that I will be informed concerning any new changes in my bugs, but that proceeding is painful. Best regards Rainer Bielefeld - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Bug 121014 - Fidelity issues
Hi all, can someone please leve a comment in above mentioned bug and explain what Fidelity issues are? Thank you Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Bug 49699 - Remove SPAM attachments
Hi, This query https://issues.apache.org/ooo/buglist.cgi?f1=attachments.submittero1=equalsquery_format=advancedresolution=---v1=non-migrated%40openoffice.orglist_id=82681 shows 201 Bugs with attachments created by user Unknown, a small sample mostly showed SPAM contents in these attachments (Bugs 57603, 17954, 34866). But some might contain appropriate sample documents (Bug 9231, 13394, ...), so unfortunately any of these attachments will have to be checked manually. SPAM should be deleted! Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Updating BZ versions for next releases
Rob Weir schrieb: Hi Rob, 1) It is reasonable for someone to report a bug using 3.4.0, 3.4.1 or 4.0.0. None of these versions are end of life so they should be allowed for new bug reports. I agree. An additional hint: for me the Version is an important distinguishing mark. Of course the exact version of appearance can be mentioned in a comment, but that is not very clear and can not be used for reliable queries. So for me selectable versions like 3.3.x or similar to narrow down version of appearance would have some benefit, and may be also for developers it might be useful to have easy access to reliable version info, what might ease to find the code and commit causing the problem. But of course, such versions only are useful if many users use them that way. 2) I don't see the purpose of AOO PleaseHelp as a milestone version. Are we overloading meaning in this field? If we really need track issues that need help we should define a keyword for this. So I'm inclined to delete this milestone version number. +1 3) I'd also like to simplify the versions across the board to be just 3.4.1, 4.0.0, etc., without the AOO prefix. +1 Discharging that ballast also eases use of regular expressions in queries 4) For Last Confirmation On, I'd like to hide values except for 4.0. We should not be confirming bugs without testing on the most recent version. Sure, new bugs can set Version to 3.4.0 or 3.4.1, but confirmation should occur on 4.0. +1 If someone can confirm a bug with 3.4.1, but no longer with 4.0, he should close that bug, or ask for help, but I can't see any benefit for a new entry Last confirmed with 3.4. or so. 5) I'll add a new Target Milestone of 4.0.1 and Version of 4.0.1-dev since it is likely that we will have a 4.0.1 release to address some of the defects that have been reported on 4.0.0. Sounds plausible. Best Regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[Bug 122803] - Make sure that developers read Bug reports related to their field of activity
Hi, can someon please proceed https://issues.apache.org/ooo/show_bug.cgi?id=122803. All discussion should be in the bug, please! Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Assigned Bugs
Hi all, in AOO bugzilla there are lots of lots of unfixed Bugs with an Assignee, but without any change for years. So, for example, today I found 722 unfixed bugs assigned to groucho...@googlemail.com (with changes within last 2 years). 2 Bugs with this assignee changed to FIXED within that time. I wonder for what it can be useful to have such an amount of assigned bugs for a single assignee. Can someone fix the gap in my knowledge? Discussion please on dev@ Best regards Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[Bug 122434] New: Using of Alias breaks Depends on Tree
Hi, can someone please have a look? Thank you Rainer - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
