Re: New committer
On 08/06/2015 12:50 PM, jan i wrote: Hi. Welcome to Manik Malhotra who just accepting being openoffice committer. rgds jan i. Welcome Manik! -- MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
New committer
Hi. Welcome to Manik Malhotra who just accepting being openoffice committer. rgds jan i.
[NOTICE] Windows build machine setted up
Hi all, finally I setted up Windows machine for dev builds. I have compiled build from AOO410 branch, for this time only in US and sk language. If nobody have better solution, I can prepare test builds. The only problem is that I cannot access people.a.o machine, I have generated ssh keys and uploaded public key to my id, but connection is still refused. I can upload builds to OneDrive or to our own server, but it has limitted bandwith so somebody need to copy it, to Apache machines (it can't be used for massive downloading). Jan - could you sent to me in private step-by-step guide for dummy about digital signing ? I can play a little with it. (for example with self generated certificate) Thanks everybody! Regards wih wishing good day, Michal Hriň - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: For Information: Reported Windows 10 problems
On Wed, 5 Aug 2015 19:44:01 -0400 Rob Weir r...@robweir.com wrote: Did some of my own testing, starting with a clean image of Windows 7 Professional x64. Installed AOO 4.1.1 and created and saved files with Writer, Calc and Impress. Did the upgrade to Windows 10. Confirmed that I could read and write the previously saved files. Tried both opening the files from within the apps as well as double-clicking the documents from the File Explorer. I experienced no file permission issues. -Rob Thanks, Rob. So we may reasonably conclude that most of the reported problems about read-only files are due to faulty user interaction with Win10. It is most helpful to have confirmation of that point. Rory On Tue, Aug 4, 2015 at 12:46 PM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: These accounts don't provide enough information to nail anything down to root causes, and some of the forum cases are not resolved one way or the other yet. My main desktop machine upgraded (with my permission) to Windows 10 Pro x64 on the evening of July 29. I already had AOO 4.1.1 and LibreOffice 4.3.5.2 installed. I just did some random opening of existing .odt and .ods files in both applications. I just opened all AOO applications from the menu window. I am unable to find any of these problems. I don't dispute that others are having some sort of trouble. I am saying it is not something I can isolate any evidence for. We need to have someone who can work with us to resolve a Bugzilla on a specific case, being able to provide screen shots or other useful information on exactly what is happening, what the messages are, etc. We also need to keep other reports separate unless the detailed actual situations are confirmed to be the same. I am happy to work with anyone who is able to do that and has a demonstrated case of post-upgrade difficulties that we can nail down. - Dennis PS: When getting the Windows File Explorer properties for a folder, the Read-only attribute box will tend to have a black square in it. This does not mean that all of the files are read only. This may be misleading some folks into thinking that is their problem. Only if there is a check-mark in the box are the files in the folder all set to read-only. (The black box apparently means there might be some read-only files in the folder below, and those are usually system files, not everything.) PPS: I have seen reports that Windows 10 Home (not Pro) has increased security safeguards. I don't know if this is related or not. PPPS: I have not attempted any fresh installs of anything. I will install a later version of LibreOffice to see if there are problems there. Based on my experience so far, I do not expect any. -Original Message- From: Rob Weir [mailto:r...@robweir.com] Sent: Tuesday, August 4, 2015 05:47 To: dev@openoffice.apache.org Subject: Re: For Information: Reported Windows 10 problems I see this as well: http://www.cnet.com/forums/discussions/windows-10-changed-all-my-documents-to-read-only/ The test to do is check the file in Windows Explorer. Right click and go to the Properties panel. If it is marked read only there, with AOO not even running, then it is an OS issue. -Rob On Tue, Aug 4, 2015 at 3:51 AM, Rory O'Farrell ofarr...@iol.ie wrote: I should stat by saying that I do not now use Windows other than an old version for access to archived files in old formats, so what I write below is based on a quick analysis from memory of recent Forum postings. There are a number of reported Windows 10 problems, some of which are being laid at the door of OpenOffice although they may be generic W10 upgrade difficulties and/or user problems with that upgrade. I list below some of the recent threads. The most common problem is that the W10 upgrade leaves all OpenOffice files (and, from other reports, other application files) in read-only form; this read-only may possibly be removable but there is no clear 100% effective path to do this (from the reports below) Other reports are of inability to open OO applications - Calc apparently being the most commonly affected. https://forum.openoffice.org/en/forum/viewtopic.php?f=9t=78470 https://forum.openoffice.org/en/forum/viewtopic.php?f=6t=78450 https://forum.openoffice.org/en/forum/viewtopic.php?f=15t=78432 https://forum.openoffice.org/en/forum/viewtopic.php?f=15t=78445 -- Rory O'Farrell ofarr...@iol.ie - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail:
[NOTICE] Windows build machine setted up
On Thursday, August 6, 2015, Michal Hriň h...@apache.org javascript:_e(%7B%7D,'cvml','h...@apache.org'); wrote: V Štvrtok, 6. august 2015 o 10:22 +0200, Michal Hriň napísal(a): Hi all, finally I setted up Windows machine for dev builds. I have compiled build from AOO410 branch, for this time only in US and sk language. If nobody have better solution, I can prepare test builds. The only problem is that I cannot access people.a.o machine, I have generated ssh keys and uploaded public key to my id, but connection is still refused. I can upload builds to OneDrive or to our own server, but it has limitted bandwith so somebody need to copy it, to Apache machines (it can't be used for massive downloading). If somebody would like to try en-US 4.1.2 Early Preview https://onedrive.live.com/redir?resid=9CF40FA60FBDCD!293authkey=!AP86Q 1h_P__6LjIithint=file%2cexe https://onedrive.live.com/redir?resid=9CF40FA60FBDCD!293authkey=!AP86Q1h_P__6LjIithint=file%2cexe Thanks for providing a binary, but I am a bit concerned that a version is made public, before the PMC have even spoken about being ready to make a release candidate or started voting on a release candidate. Is this coordinated with the release manager for 4.1.2 ? Please do not misunderstand me, I think it is great that work is being done, I am just surprised we are ready to go public with 4.1.2 even as a pre-view. rgds jan i Jan - could you sent to me in private step-by-step guide for dummy about digital signing ? I can play a little with it. (for example with self generated certificate) Thanks everybody! Regards wih wishing good day, Michal Hriň - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Sent from My iPad, sorry for any misspellings.
4.1.2_release_blocker requested: [Issue 126447] When using LanguageTools, toggling the checkbox check grammar in the spell checker removes content
Marcus mar...@apache.org has asked for 4.1.2_release_blocker: Issue 126447: When using LanguageTools, toggling the checkbox check grammar in the spell checker removes content https://bz.apache.org/ooo/show_bug.cgi?id=126447 --- Comment #1 from Marcus mar...@apache.org --- @Stefan: Thanks for the patch. Seems to be an easy fix. @All: I suggest to accept this issue and fix for the 4.1.2 release. Reasons: - Preventing data loss - Easy fix - Low risk - Support the work from AOO contributors - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: STATE OF AOO: Overall Bugzilla Activity through July 2015
Thanks for generating the numbers. Even when it is no surprise that we have many unsolved issues, it's always good to know the current values. In general I agree with Juergen and Roberto, we should focus on the newer times of AOO. Suggestion: To get rid of old issues we need to close all issues that are already in a state short before closure [*]: Duplicate, Irreproducible, Obsolete, Not_an_issue, Verified, Wont_fix As second step we can close all issues that are in status Resolved and last updated months/years ago. Then we have a much lower base of open issues and can filter better about age, importantance and severity. Finally it's then easier to decide what to do with the remaining open issues. [*] This makes it necessary to stop all BZ notification mails. Otherwise we get flooded by billions of mails and get hit by the Infra team all summer long. ;-) Marcus Am 08/06/2015 04:56 AM, schrieb Dennis E. Hamilton: In looking for visible indicators of project activity, I created an overview of Bugzilla activity from November 2012 through July 2015. This is a high-level view of gross activity and does not provide fine details. There is still an interesting picture. My complete tabulation is available in a PDF document at http://svn.apache.org/repos/asf/openoffice/pmc/project-state/2015-07-BZ-OverallActivity-2015-08-05-dh.pdf. Here is a summary of what I captured. 2012-11: #121299 First new issue in the Bugzilla of the AOO Top Level Project. 2015-07: #126439 Last new issue in the Bugzilla at the end of July, 2015. By years, (2012 and 2015 partial) 20122013 2014 2015 9292136 1739441 BZ items/month 133 198170 65 New issues/month (averages are rounded to whole numbers) As of 2015-08-05 * the oldest open issue is #497 created 2001-03-02 * 24115 issues still open from before November, 2012 * 2232 issues remain open of the 5139 new issues from November, 2012 through July, 2015 * 192 issues remain open of the 452 of those created in the first 7 months of 2015 The most noticeable aspects are the steady decline in monthly Bugzilla items (i.e., entries of all kinds) and in the number of those that are introduction of new issues. The next observation is of the tremendous number of open issues that preceded the commencement of Apache OpenOffice following the incubation period begun in June 2011. To see other patterns, it is necessary to examine finer details. I propose to do that only for 2015, so we have a better community understanding of what is happening with issues at this time. I have no interpretation of these trends, and the burden inherited by Apache OpenOffice, other than noticing what they are. -- Dennis E. Hamilton - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: STATE OF AOO: Overall Bugzilla Activity through July 2015
Marcus, the queries I did for identification of open issues found only issues with no resolution of any kind. That automatically excluded issues with any of DUPLICATE, ..., WON'T FIX, and CLOSED status. Older open issues, some from long before Apache OpenOffice was established, continue to receive discussion and comments and, even in 2015, sometimes become resolved, including with fixes. I think it is good to hold onto the history simply to be able to reflect that. I agree that immediate concerns are best explored by looking more deeply into the 2015 issues and discussions to gain better perspective. I suspect the older open issues to look more closely at first are ones that are still being discussed, including being duplicated by new issue reports. - Dennis -Original Message- From: Marcus [mailto:marcus.m...@wtnet.de] Sent: Thursday, August 6, 2015 05:18 To: dev@openoffice.apache.org Subject: Re: STATE OF AOO: Overall Bugzilla Activity through July 2015 Thanks for generating the numbers. Even when it is no surprise that we have many unsolved issues, it's always good to know the current values. In general I agree with Juergen and Roberto, we should focus on the newer times of AOO. Suggestion: To get rid of old issues we need to close all issues that are already in a state short before closure [*]: Duplicate, Irreproducible, Obsolete, Not_an_issue, Verified, Wont_fix As second step we can close all issues that are in status Resolved and last updated months/years ago. Then we have a much lower base of open issues and can filter better about age, importantance and severity. Finally it's then easier to decide what to do with the remaining open issues. [*] This makes it necessary to stop all BZ notification mails. Otherwise we get flooded by billions of mails and get hit by the Infra team all summer long. ;-) Marcus [ ... ] - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: For Information: Reported Windows 10 problems
On Thu, Aug 6, 2015 at 2:04 AM, Rory O'Farrell ofarr...@iol.ie wrote: On Wed, 5 Aug 2015 19:44:01 -0400 Rob Weir r...@robweir.com wrote: Did some of my own testing, starting with a clean image of Windows 7 Professional x64. Installed AOO 4.1.1 and created and saved files with Writer, Calc and Impress. Did the upgrade to Windows 10. Confirmed that I could read and write the previously saved files. Tried both opening the files from within the apps as well as double-clicking the documents from the File Explorer. I experienced no file permission issues. -Rob Thanks, Rob. So we may reasonably conclude that most of the reported problems about read-only files are due to faulty user interaction with Win10. It is most helpful to have confirmation of that point. We can only really say that there does not seem to be a problem with the most straightforward upgrade scenario. There may be an issue, with Windows or with AOO, in some more complicated scenarios. Or not. It might be worth asking a few questions to see if there is a pattern: 1) What version of Windows did you upgrade from? 2) 32 bit or 64 bit? 3) The Windows 10 upgrade gives three options: a) Fresh install, b) Preserve Data and Programs and c) Preserve data only. Which did you do? 4) Where were the documents stored that AOO sees as read-only? Local HD? USB stick? Cloud storage? 5) Do you see this problem with other applications and their documents, or only with AOO? Regards, -Rob Rory On Tue, Aug 4, 2015 at 12:46 PM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: These accounts don't provide enough information to nail anything down to root causes, and some of the forum cases are not resolved one way or the other yet. My main desktop machine upgraded (with my permission) to Windows 10 Pro x64 on the evening of July 29. I already had AOO 4.1.1 and LibreOffice 4.3.5.2 installed. I just did some random opening of existing .odt and .ods files in both applications. I just opened all AOO applications from the menu window. I am unable to find any of these problems. I don't dispute that others are having some sort of trouble. I am saying it is not something I can isolate any evidence for. We need to have someone who can work with us to resolve a Bugzilla on a specific case, being able to provide screen shots or other useful information on exactly what is happening, what the messages are, etc. We also need to keep other reports separate unless the detailed actual situations are confirmed to be the same. I am happy to work with anyone who is able to do that and has a demonstrated case of post-upgrade difficulties that we can nail down. - Dennis PS: When getting the Windows File Explorer properties for a folder, the Read-only attribute box will tend to have a black square in it. This does not mean that all of the files are read only. This may be misleading some folks into thinking that is their problem. Only if there is a check-mark in the box are the files in the folder all set to read-only. (The black box apparently means there might be some read-only files in the folder below, and those are usually system files, not everything.) PPS: I have seen reports that Windows 10 Home (not Pro) has increased security safeguards. I don't know if this is related or not. PPPS: I have not attempted any fresh installs of anything. I will install a later version of LibreOffice to see if there are problems there. Based on my experience so far, I do not expect any. -Original Message- From: Rob Weir [mailto:r...@robweir.com] Sent: Tuesday, August 4, 2015 05:47 To: dev@openoffice.apache.org Subject: Re: For Information: Reported Windows 10 problems I see this as well: http://www.cnet.com/forums/discussions/windows-10-changed-all-my-documents-to-read-only/ The test to do is check the file in Windows Explorer. Right click and go to the Properties panel. If it is marked read only there, with AOO not even running, then it is an OS issue. -Rob On Tue, Aug 4, 2015 at 3:51 AM, Rory O'Farrell ofarr...@iol.ie wrote: I should stat by saying that I do not now use Windows other than an old version for access to archived files in old formats, so what I write below is based on a quick analysis from memory of recent Forum postings. There are a number of reported Windows 10 problems, some of which are being laid at the door of OpenOffice although they may be generic W10 upgrade difficulties and/or user problems with that upgrade. I list below some of the recent threads. The most common problem is that the W10 upgrade leaves all OpenOffice files (and, from other reports, other application files) in read-only form; this read-only may possibly be removable but there is no clear 100% effective path to do this (from the reports below) Other reports are
Re: For Information: Reported Windows 10 problems
On Thu, 6 Aug 2015 09:38:58 -0400 Rob Weir r...@robweir.com wrote: On Thu, Aug 6, 2015 at 2:04 AM, Rory O'Farrell ofarr...@iol.ie wrote: On Wed, 5 Aug 2015 19:44:01 -0400 Rob Weir r...@robweir.com wrote: Did some of my own testing, starting with a clean image of Windows 7 Professional x64. Installed AOO 4.1.1 and created and saved files with Writer, Calc and Impress. Did the upgrade to Windows 10. Confirmed that I could read and write the previously saved files. Tried both opening the files from within the apps as well as double-clicking the documents from the File Explorer. I experienced no file permission issues. -Rob Thanks, Rob. So we may reasonably conclude that most of the reported problems about read-only files are due to faulty user interaction with Win10. It is most helpful to have confirmation of that point. We can only really say that there does not seem to be a problem with the most straightforward upgrade scenario. There may be an issue, with Windows or with AOO, in some more complicated scenarios. Or not. It might be worth asking a few questions to see if there is a pattern: 1) What version of Windows did you upgrade from? 2) 32 bit or 64 bit? 3) The Windows 10 upgrade gives three options: a) Fresh install, b) Preserve Data and Programs and c) Preserve data only. Which did you do? 4) Where were the documents stored that AOO sees as read-only? Local HD? USB stick? Cloud storage? 5) Do you see this problem with other applications and their documents, or only with AOO? Regards, -Rob I've filed this reply, Rob, and will ask these questions when the problem arises. Rory Rory On Tue, Aug 4, 2015 at 12:46 PM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: These accounts don't provide enough information to nail anything down to root causes, and some of the forum cases are not resolved one way or the other yet. My main desktop machine upgraded (with my permission) to Windows 10 Pro x64 on the evening of July 29. I already had AOO 4.1.1 and LibreOffice 4.3.5.2 installed. I just did some random opening of existing .odt and .ods files in both applications. I just opened all AOO applications from the menu window. I am unable to find any of these problems. I don't dispute that others are having some sort of trouble. I am saying it is not something I can isolate any evidence for. We need to have someone who can work with us to resolve a Bugzilla on a specific case, being able to provide screen shots or other useful information on exactly what is happening, what the messages are, etc. We also need to keep other reports separate unless the detailed actual situations are confirmed to be the same. I am happy to work with anyone who is able to do that and has a demonstrated case of post-upgrade difficulties that we can nail down. - Dennis PS: When getting the Windows File Explorer properties for a folder, the Read-only attribute box will tend to have a black square in it. This does not mean that all of the files are read only. This may be misleading some folks into thinking that is their problem. Only if there is a check-mark in the box are the files in the folder all set to read-only. (The black box apparently means there might be some read-only files in the folder below, and those are usually system files, not everything.) PPS: I have seen reports that Windows 10 Home (not Pro) has increased security safeguards. I don't know if this is related or not. PPPS: I have not attempted any fresh installs of anything. I will install a later version of LibreOffice to see if there are problems there. Based on my experience so far, I do not expect any. -Original Message- From: Rob Weir [mailto:r...@robweir.com] Sent: Tuesday, August 4, 2015 05:47 To: dev@openoffice.apache.org Subject: Re: For Information: Reported Windows 10 problems I see this as well: http://www.cnet.com/forums/discussions/windows-10-changed-all-my-documents-to-read-only/ The test to do is check the file in Windows Explorer. Right click and go to the Properties panel. If it is marked read only there, with AOO not even running, then it is an OS issue. -Rob On Tue, Aug 4, 2015 at 3:51 AM, Rory O'Farrell ofarr...@iol.ie wrote: I should stat by saying that I do not now use Windows other than an old version for access to archived files in old formats, so what I write below is based on a quick analysis from memory of recent Forum postings. There are a number of reported Windows 10 problems, some of which are being laid at the door of OpenOffice although they may be generic W10 upgrade difficulties and/or user problems with that upgrade. I list below some of the recent threads. The most common
Re: STATE OF AOO: Overall Bugzilla Activity through July 2015
On Thu, Aug 6, 2015 at 8:18 AM, Marcus marcus.m...@wtnet.de wrote: Thanks for generating the numbers. Even when it is no surprise that we have many unsolved issues, it's always good to know the current values. From the stats perspective, what is interesting is when you have a real de-duplicated, validated set of defect reports. That is not what we have now. We have numerous duplicates, open issues that should be closed as fixed, and even many support questions masquerading as bug reports. Trying to interpret raw defect report stats is a hard problem. In general I agree with Juergen and Roberto, we should focus on the newer times of AOO. Suggestion: To get rid of old issues we need to close all issues that are already in a state short before closure [*]: Duplicate, Irreproducible, Obsolete, Not_an_issue, Verified, Wont_fix As second step we can close all issues that are in status Resolved and last updated months/years ago. Then we have a much lower base of open issues and can filter better about age, importantance and severity. Finally it's then easier to decide what to do with the remaining open issues. This is also an area where new QA volunteers can really make a difference. If you recall, a few years ago we did a call for QA volunteers and had almost a dozen of them going through old issues to try to validate them in the current AOO build. This is a task that can be crowd sourced,...if there is someone who volunteers to organize the effort, assign bugs for other volunteers to look at, answer questions, give feedback, etc. Another step we could take is to send a reminder note to all reports of bugs that have been marked as needs more information. Say that the issue will be closed as not reproducible if the needed information is not made available in, say 4 weeks. Of course, such issues can always be reopened if information comes in later. [*] This makes it necessary to stop all BZ notification mails. Otherwise we get flooded by billions of mails and get hit by the Infra team all summer long. ;-) A good reminder ;-) Regards, -Rob Marcus Am 08/06/2015 04:56 AM, schrieb Dennis E. Hamilton: In looking for visible indicators of project activity, I created an overview of Bugzilla activity from November 2012 through July 2015. This is a high-level view of gross activity and does not provide fine details. There is still an interesting picture. My complete tabulation is available in a PDF document at http://svn.apache.org/repos/asf/openoffice/pmc/project-state/2015-07-BZ-OverallActivity-2015-08-05-dh.pdf. Here is a summary of what I captured. 2012-11: #121299 First new issue in the Bugzilla of the AOO Top Level Project. 2015-07: #126439 Last new issue in the Bugzilla at the end of July, 2015. By years, (2012 and 2015 partial) 20122013 2014 2015 9292136 1739441 BZ items/month 133 198170 65 New issues/month (averages are rounded to whole numbers) As of 2015-08-05 * the oldest open issue is #497 created 2001-03-02 * 24115 issues still open from before November, 2012 * 2232 issues remain open of the 5139 new issues from November, 2012 through July, 2015 * 192 issues remain open of the 452 of those created in the first 7 months of 2015 The most noticeable aspects are the steady decline in monthly Bugzilla items (i.e., entries of all kinds) and in the number of those that are introduction of new issues. The next observation is of the tremendous number of open issues that preceded the commencement of Apache OpenOffice following the incubation period begun in June 2011. To see other patterns, it is necessary to examine finer details. I propose to do that only for 2015, so we have a better community understanding of what is happening with issues at this time. I have no interpretation of these trends, and the burden inherited by Apache OpenOffice, other than noticing what they are. -- Dennis E. Hamilton - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: STATE OF AOO: Overall Bugzilla Activity through July 2015
On 06/08/15 08:17, Roberto Galoppini wrote: Thanks Dennis for doing that, great job. I agree we should look deeper into what happened in 2015 only. Roberto 2015-08-06 4:56 GMT+02:00 Dennis E. Hamilton orc...@apache.org: In looking for visible indicators of project activity, I created an overview of Bugzilla activity from November 2012 through July 2015. This is a high-level view of gross activity and does not provide fine details. There is still an interesting picture. My complete tabulation is available in a PDF document at http://svn.apache.org/repos/asf/openoffice/pmc/project-state/2015-07-BZ-OverallActivity-2015-08-05-dh.pdf . Here is a summary of what I captured. 2012-11: #121299 First new issue in the Bugzilla of the AOO Top Level Project. 2015-07: #126439 Last new issue in the Bugzilla at the end of July, 2015. By years, (2012 and 2015 partial) 20122013 2014 2015 9292136 1739441 BZ items/month 133 198170 65 New issues/month (averages are rounded to whole numbers) As of 2015-08-05 * the oldest open issue is #497 created 2001-03-02 * 24115 issues still open from before November, 2012 * 2232 issues remain open of the 5139 new issues from November, 2012 through July, 2015 * 192 issues remain open of the 452 of those created in the first 7 months of 2015 The most noticeable aspects are the steady decline in monthly Bugzilla items (i.e., entries of all kinds) and in the number of those that are introduction of new issues. The next observation is of the tremendous number of open issues that preceded the commencement of Apache OpenOffice following the incubation period begun in June 2011. To see other patterns, it is necessary to examine finer details. I propose to do that only for 2015, so we have a better community understanding of what is happening with issues at this time. I have no interpretation of these trends, and the burden inherited by Apache OpenOffice, other than noticing what they are. The numbers are not really relevant. We had ever a huge backlog of issues that will never be fixed and where many of them are probably obsolete or invalid today. You can also delete them all and can start from scratch (by the way that would have been my preferred solution for AOO after we migrated to Apache). New issues in the last year (maybe last 2) are more valid and deserves more attention because they are coming from real users who are using probably one of the newer releases. But what do you expect of these numbers what you don't already know? You can run more statistic but the numbers won't become better. More important is to think about a solution to really work on these issues and reduce the number. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Windows build machine setted up
On Thursday, August 6, 2015, Michal Hriň h...@apache.org wrote: Hi all, finally I setted up Windows machine for dev builds. I have compiled build from AOO410 branch, for this time only in US and sk language. If nobody have better solution, I can prepare test builds. The only problem is that I cannot access people.a.o machine, I have generated ssh keys and uploaded public key to my id, but connection is still refused. I can upload builds to OneDrive or to our own server, but it has limitted bandwith so somebody need to copy it, to Apache machines (it can't be used for massive downloading). Jan - could you sent to me in private step-by-step guide for dummy about digital signing ? I can play a little with it. (for example with self generated certificate) I wrote it in an earlier email, search for digital signing. You need a verisign account and only andrea has a AOO account and you need a simple modification of the build procedure. Andrea wanted to add me earlier but due to I believe some complications it never happened. Anyhow the way I suggested digital signing, was an idea which I tested, but others might have different ideas about how to do it. First step would be to agree on what should be signed (only the setup exe, the runtime exe, the runtime dll and jars). A good digital signing (like my proposal) contain it all. rgds jan i Thanks everybody! Regards wih wishing good day, Michal Hriň - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org javascript:; For additional commands, e-mail: dev-h...@openoffice.apache.org javascript:; -- Sent from My iPad, sorry for any misspellings.
Open office FAQ
Hello sirs, First of all, thank you for developing such a useful Software. Very good features and easy in use. Due to my volunteering program I translate tutorials, faq pages into Russian and would be really glad to translate your FAQ page https://www.openoffice.org/faq.html as well. I hope it will help Russian users. Please let me know if it is possible. Regards, Ivanka -- Amazing Deep Sea Creatures http://magazine.good.is/videos/amazing-deep-sea-creatures | Outsmart Your Own Biases https://hbr.org/2015/05/outsmart-your-own-biases | Why Do I Translate? http://www.coupofy.com/translation/ ᐧ
Re: [NOTICE] Windows build machine setted up
V Štvrtok, 6. august 2015 o 10:22 +0200, Michal Hriň napísal(a): Hi all, finally I setted up Windows machine for dev builds. I have compiled build from AOO410 branch, for this time only in US and sk language. If nobody have better solution, I can prepare test builds. The only problem is that I cannot access people.a.o machine, I have generated ssh keys and uploaded public key to my id, but connection is still refused. I can upload builds to OneDrive or to our own server, but it has limitted bandwith so somebody need to copy it, to Apache machines (it can't be used for massive downloading). If somebody would like to try en-US 4.1.2 Early Preview https://onedrive.live.com/redir?resid=9CF40FA60FBDCD!293authkey=!AP86Q 1h_P__6LjIithint=file%2cexe Jan - could you sent to me in private step-by-step guide for dummy about digital signing ? I can play a little with it. (for example with self generated certificate) Thanks everybody! Regards wih wishing good day, Michal Hriň - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Reporting broken download link
Yeah thanks. 3rd time was a charm --JHS From: Roberto Galoppini [mailto:roberto.galopp...@gmail.com] Sent: Wednesday, August 5, 2015 1:56 AM To: dev dev@openoffice.apache.org; Jonathan Stanwood j...@stanwoodlaw.com Subject: Re: Reporting broken download link It works for me, may be it was a temporary problem. Thanks, Roberto 2015-08-04 18:22 GMT+02:00 Jonathan Stanwood j...@stanwoodlaw.com mailto:j...@stanwoodlaw.com : http://sourceforge.net/projects/openofficeorg.mirror/files/4.1.1/binaries/en http://sourceforge.net/projects/openofficeorg.mirror/files/4.1.1/binaries/en-US/Apache_OpenOffice_4.1.1_Win_x86_install_en-US.exe/download -US/Apache_OpenOffice_4.1.1_Win_x86_install_en-US.exe/download Doesn't work :( Jonathan H. Stanwood, Esq. 8 Penn Center 1628 J.F.K. Blvd, Suite 1000 Philadelphia, Pa 19103 (215) 569-1040 www.stanwoodlaw.com http://www.stanwoodlaw.com
