4.1.4_release_blocker canceled: [Issue 127253] Update the banners with the new ASF Logo
Jim Jagielski has canceled Matthias Seidel 's request for 4.1.4_release_blocker: Issue 127253: Update the banners with the new ASF Logo https://bz.apache.org/ooo/show_bug.cgi?id=127253 --- Comment #15 from Jim Jagielski --- Not a blocker - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.4_release_blocker canceled: [Issue 122376] Splash Screen shows wrong credits-URL
Jim Jagielski has canceled Matthias Seidel 's request for 4.1.4_release_blocker: Issue 122376: Splash Screen shows wrong credits-URL https://bz.apache.org/ooo/show_bug.cgi?id=122376 --- Comment #8 from Jim Jagielski --- Not a blocker (same reason as Issue 127253) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Status: 4.1.4
I am going thru the proposed blockers in anticipation of a AOO 4.1.4 release. I have not approved the 2 graphics-related mods, simply because even though they look like they might be easy, I don't want to subject ourselves to the risk, even as small as it might be. Plus, good PR for 4.2.0. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Status: 4.1.4
Hi Jim Am .05.2017, 15:53 Uhr, schrieb Jim Jagielski : I am going thru the proposed blockers in anticipation of a AOO 4.1.4 release. I have not approved the 2 graphics-related mods, simply because even though they look like they might be easy, I don't want to subject ourselves to the risk, even as small as it might be. Plus, good PR for 4.2.0. I'm fine with this. From the release criteria point of view it's not really a blocker. Does this also mean, that you take over the Release Nanager? Regards, Raphael -- My introduction https://youtu.be/Ln4vly5sxYU - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
There are some tar.gz in the 4.1.4 source
Hi all There are some tar.gz in the 4.1.4 source in ext_source. They should not be there. we have to remove them before the release. Make sure, that you always run clean before committing stuff. Else we have binaries inside the source. Regards, Raphael -- My introduction https://youtu.be/Ln4vly5sxYU - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Problem with Open Office before and after installing new update
Le 22/05/2017 à 10:16, Rory O'Farrell a écrit : On Mon, 22 May 2017 09:57:31 +0200 Peter Kovacs wrote: Thanks for the sum up. Still I think we should find a solution. So i adf backup at the start of editing session to the list. Is there a bug for this? There certainly ought be, but I cannot point to one. I think Hagar has remarked on Forum of one instance of spellcheck or file corruption on his (work) Windows system, and with great respect, that might be due to a freak close down on his part. In this sort of fault finding the user reports of their actions are "unreliable", as they often feel they are being trapped into an admission of improper computer use. In ten years of heavy use of StarOffice/OO (last years on linux) I have experienced file corruption or spellcheck problems on very few occasions, caused by unexpected power cuts in storms. My computer experience goes back to 1965 (Fortran II on an IBM 1640), so I am aware of the need for system in their use, Rory There is a bug report for the ### and for the dictionary issue (but the latter was closed as fixed). Never heard of a feature request to have a backup of the registrymodification.xcu file. Sounds a good idea but still needs tweaking from user to restore the former file. As for the spellcheck corruption, I noticed quite recently that it could be in fact a temporary glitch. It happened on a big file (25MB), sometimes all the text is underlined and sometimes there is no underline at all (even where there should be). This behavior disappear after some time (haven't yet investigated what is needed, reboot or Windows session...). Hagar - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Problem with Open Office before and after installing new update
On Tue, 23 May 2017 22:11:37 +0200 Hagar Delest wrote: > Le 22/05/2017 à 10:16, Rory O'Farrell a écrit : > > On Mon, 22 May 2017 09:57:31 +0200 > > Peter Kovacs wrote: > >> Thanks for the sum up. > >> > >> Still I think we should find a solution. > >> So i adf backup at the start of editing session to the list. > >> > >> Is there a bug for this? > > There certainly ought be, but I cannot point to one. > > > > I think Hagar has remarked on Forum of one instance of spellcheck or file > > corruption on his (work) Windows system, and with great respect, that might > > be due to a freak close down on his part. In this sort of fault finding > > the user reports of their actions are "unreliable", as they often feel they > > are being trapped into an admission of improper computer use. > > > > In ten years of heavy use of StarOffice/OO (last years on linux) I have > > experienced file corruption or spellcheck problems on very few occasions, > > caused by unexpected power cuts in storms. My computer experience goes > > back to 1965 (Fortran II on an IBM 1640), so I am aware of the need for > > system in their use, > > > > Rory > There is a bug report for the ### and for the dictionary issue (but the > latter was closed as fixed). > Never heard of a feature request to have a backup of the > registrymodification.xcu file. Sounds a good idea but still needs tweaking > from user to restore the former file. Hager, My thoughts on a backup were that the file opened at start of an editing session should be backed up, so that in the event that the edited file corrupted (the ### problem) the previous version remained available. It is bad enough to lose a session of edits, but how much worse to lose the entire file as often occurs with the ### problem Having regard to the large size of current hard disks, I feel that this backup procedure (might it need to be a backup of a backup?) should be enabled by default > > As for the spellcheck corruption, I noticed quite recently that it could be > in fact a temporary glitch. It happened on a big file (25MB), sometimes all > the text is underlined and sometimes there is no underline at all (even where > there should be). This behavior disappear after some time (haven't yet > investigated what is needed, reboot or Windows session...) Perhaps such a file is at the limit of what OO can comfortably handle. I know from my own experience that large files can be slow to format correctly, depending where in the file the cursor was last positioned. The formatting seems to start at the cursor position and seems to take several passes through the file until it stabilises. The ### problem you report may be an instance of this and might have cleared with the stabilisation of the formatting. Rory > > Hagar > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: There are some tar.gz in the 4.1.4 source
Raphael Bircher wrote: There are some tar.gz in the 4.1.4 source in ext_source. They should not be there. we have to remove them before the release. There is no "4.1.4 source" since, as you say, we haven't released 4.1.4 yet. If you mean that http://svn.apache.org/viewvc/openoffice/branches/AOO414/ contains external sources, this is not an issue at all: the source package (so the real "4.1.4 source") is prepared by a script that removes the extra files. Make sure, that you always run clean before committing stuff. Else we have binaries inside the source. If you look at the link above, you will see that nobody committed to it since it was created (as a copy of the 4.1.3 sources). So nobody committed additional stuff by mistake, it was already there. If you want to take a look at the script (that actually needs some polishing) you can probably find it in the release blockers, or just ask again and I will find the link. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: There are some tar.gz in the 4.1.4 source
Hi Andrea Am .05.2017, 23:10 Uhr, schrieb Andrea Pescetti : Raphael Bircher wrote: There are some tar.gz in the 4.1.4 source in ext_source. They should not be there. we have to remove them before the release. There is no "4.1.4 source" since, as you say, we haven't released 4.1.4 yet. If you mean that http://svn.apache.org/viewvc/openoffice/branches/AOO414/ contains external sources, this is not an issue at all: the source package (so the real "4.1.4 source") is prepared by a script that removes the extra files. Make sure, that you always run clean before committing stuff. Else we have binaries inside the source. If you look at the link above, you will see that nobody committed to it since it was created (as a copy of the 4.1.3 sources). So nobody committed additional stuff by mistake, it was already there. If you want to take a look at the script (that actually needs some polishing) you can probably find it in the release blockers, or just ask again and I will find the link. Thanks for that information, than all is ok. Regards Raphael -- My introduction https://youtu.be/Ln4vly5sxYU - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Problem with Open Office before and after installing new update
Le 23/05/2017 à 22:44, Rory O'Farrell a écrit : On Tue, 23 May 2017 22:11:37 +0200 Hagar Delest wrote: Le 22/05/2017 à 10:16, Rory O'Farrell a écrit : On Mon, 22 May 2017 09:57:31 +0200 Peter Kovacs wrote: Thanks for the sum up. Still I think we should find a solution. So i adf backup at the start of editing session to the list. Is there a bug for this? There certainly ought be, but I cannot point to one. I think Hagar has remarked on Forum of one instance of spellcheck or file corruption on his (work) Windows system, and with great respect, that might be due to a freak close down on his part. In this sort of fault finding the user reports of their actions are "unreliable", as they often feel they are being trapped into an admission of improper computer use. In ten years of heavy use of StarOffice/OO (last years on linux) I have experienced file corruption or spellcheck problems on very few occasions, caused by unexpected power cuts in storms. My computer experience goes back to 1965 (Fortran II on an IBM 1640), so I am aware of the need for system in their use, Rory There is a bug report for the ### and for the dictionary issue (but the latter was closed as fixed). Never heard of a feature request to have a backup of the registrymodification.xcu file. Sounds a good idea but still needs tweaking from user to restore the former file. Hager, My thoughts on a backup were that the file opened at start of an editing session should be backed up, so that in the event that the edited file corrupted (the ### problem) the previous version remained available. It is bad enough to lose a session of edits, but how much worse to lose the entire file as often occurs with the ### problem Having regard to the large size of current hard disks, I feel that this backup procedure (might it need to be a backup of a backup?) should be enabled by default I thought the backup proposed by Peter was for the registrymodification file. After second reading, it was about any file at all. Understood. Of course, that should be the standard process. I think that the new file should be written as a temporary file next to the original one and the original deleted and the new one renamed after the system has confirmation from the OS that the save is complete. I think that when saving a file in MS Office, we can see such temporary files appear and disappear when saving. As for the spellcheck corruption, I noticed quite recently that it could be in fact a temporary glitch. It happened on a big file (25MB), sometimes all the text is underlined and sometimes there is no underline at all (even where there should be). This behavior disappear after some time (haven't yet investigated what is needed, reboot or Windows session...) Perhaps such a file is at the limit of what OO can comfortably handle. I know from my own experience that large files can be slow to format correctly, depending where in the file the cursor was last positioned. The formatting seems to start at the cursor position and seems to take several passes through the file until it stabilises. The ### problem you report may be an instance of this and might have cleared with the stabilisation of the formatting. As far as I remember, even waiting for a long time doesn't change anything. No real time to investigate when that file is open but will try to record if there is something special. Hagar - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Fwd: Problem with Open Office before and after installing new update
I have made some thought on file security. I think that the backup strategy is not good at all. I rather propose to copy the original to a temp folder. Then we work on the file and at save time we save first the temp file and then copy it back. Before we copy back we check the health of the copy making sure it's in good state. With this strategy we should always have a working copy available. Haven't check the necessary changes yet. It is just an idea. Am 23. Mai 2017 23:25:02 MESZ schrieb Hagar Delest : >Le 23/05/2017 à 22:44, Rory O'Farrell a écrit : >> On Tue, 23 May 2017 22:11:37 +0200 >> Hagar Delest wrote: >>> Le 22/05/2017 à 10:16, Rory O'Farrell a écrit : On Mon, 22 May 2017 09:57:31 +0200 Peter Kovacs wrote: > Thanks for the sum up. > > Still I think we should find a solution. > So i adf backup at the start of editing session to the list. > > Is there a bug for this? There certainly ought be, but I cannot point to one. I think Hagar has remarked on Forum of one instance of spellcheck >or file corruption on his (work) Windows system, and with great >respect, that might be due to a freak close down on his part. In this >sort of fault finding the user reports of their actions are >"unreliable", as they often feel they are being trapped into an >admission of improper computer use. In ten years of heavy use of StarOffice/OO (last years on linux) I >have experienced file corruption or spellcheck problems on very few >occasions, caused by unexpected power cuts in storms. My computer >experience goes back to 1965 (Fortran II on an IBM 1640), so I am aware >of the need for system in their use, Rory >>> There is a bug report for the ### and for the dictionary issue (but >the latter was closed as fixed). >>> Never heard of a feature request to have a backup of the >registrymodification.xcu file. Sounds a good idea but still needs >tweaking from user to restore the former file. >> >> Hager, >> >> My thoughts on a backup were that the file opened at start of an >editing session should be backed up, so that in the event that the >edited file corrupted (the ### problem) the previous version remained >available. It is bad enough to lose a session of edits, but how much >worse to lose the entire file as often occurs with the ### problem >Having regard to the large size of current hard disks, I feel that this >backup procedure (might it need to be a backup of a backup?) should be >enabled by default >I thought the backup proposed by Peter was for the registrymodification >file. After second reading, it was about any file at all. Understood. >Of course, that should be the standard process. >I think that the new file should be written as a temporary file next to >the original one and the original deleted and the new one renamed after >the system has confirmation from the OS that the save is complete. >I think that when saving a file in MS Office, we can see such temporary >files appear and disappear when saving. > >>> As for the spellcheck corruption, I noticed quite recently that it >could be in fact a temporary glitch. It happened on a big file (25MB), >sometimes all the text is underlined and sometimes there is no >underline at all (even where there should be). This behavior disappear >after some time (haven't yet investigated what is needed, reboot or >Windows session...) >> Perhaps such a file is at the limit of what OO can comfortably >handle. I know from my own experience that large files can be slow to >format correctly, depending where in the file the cursor was last >positioned. The formatting seems to start at the cursor position and >seems to take several passes through the file until it stabilises. The >### problem you report may be an instance of this and might have >cleared with the stabilisation of the formatting. >As far as I remember, even waiting for a long time doesn't change >anything. >No real time to investigate when that file is open but will try to >record if there is something special. > >Hagar > > >- >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
