Re: [PROPOSAL] Managing branches for future releases

[Mechtilde]

+1

so we can also show to be ready to fix important bugs in time.

this is also a statement to the community

Regards

Mechtilde

Am 25.10.2017 um 01:00 schrieb Patricia Shanahan:
> 
> 
> On 10/24/2017 2:34 PM, Kay Schenk wrote:
>>
>> On 10/24/2017 01:25 PM, Andrea Pescetti wrote:
>>> I'm starting a short series of occasional posts to capture the
>>> current collective state of mind on the next release. I'll float them
>>> here for refinement or lazy consensus, and then we may want to reuse
>>> this text in wiki or blog posts to avoid repeating the same concepts
>>> over and over.
>>>
>>> Let's start with branches.
>>>
>>> We all wish 4.1.4 to be the last 4.1.x release.
>>>
>>> We currently have an AOO415 branch at
>>> http://svn.apache.org/viewvc/openoffice/branches/AOO415/ ; this
>>> branch is a copy of AOO414 (that resulted in OpenOffice 4.1.4). The
>>> AOO415 branch will result in a release ONLY if we have some important
>>> bug fixes to release and trunk is not ready yet. No new features,
>>> even small enhancements, are added to it. No commits to AOO415 happen
>>> without appropriate mailing list discussions (dev or security,
>>> depending on cases).
>>>
>>> Trunk is where all development happens. It will be branched for a new
>>> release (like, an AOO420 branch - name still provisional) when the
>>> code is mature: beta or even RC. Until then, we simply keep working
>>> on trunk as we are doing now.
>>>
>>> In case we need to commit to a branch, any changes are still
>>> committed to trunk first and then merged to branches using SVN merge
>>> in all situations when this is possible (i.e., when there are no
>>> merge conflicts). The mergeinfo for AOO414 and AOO415 isn't clear, so
>>> we'll have to make sure that trunk contains all fixes done there (or
>>> equivalent in case of conflicts) and, done that, we commit to AOO415
>>> only if:
>>> 1. The fix is important and agreed upon on the relevant list
>>> 2. The commit is done with "svn merge" starting from a trunk commit
>>>
>>> This will ensure that we can shift the focus to trunk while still
>>> keeping a branch that remains ready for a quick release if needed. If
>>> we are never in this situation, the next release will be from the
>>> current trunk and AOO415 will never result in a release.
>>>
>>> Regards,
>>>    Andrea.
>>
>> Would it be more clear to just remove the AOO415 branch and only
>> re-instate it if needed (hopefully not). I don't see anything in
>> AOO415 that wasn't included in AOO414.
>>
> 
> The decision to keep the 4.1.5 branch around came out of a discussion on
> the security mailing list. The potential problem is that someday we may
> be faced with a bug for which we need to get a fix out into the field as
> soon as possible.
> 
> Because of the sheer size of AOO, it takes time to get set up for a
> release. The idea is to do as much as we can to prepare without
> committing to a release. I have a check-out of AOO415 built. As the
> version number changes get incorporated I'll update and rebuild. Not
> having to wait for the branch to be prepared, check it out, and do a
> full build reduces by about a day the time it would take from knowing a
> fix to having it built, tested, and checked in.
> 
> I would like to make this an on-going policy. As soon as we ship 4.2.0,
> we remove the AOO415 branch but create AOO421, identical except for
> version numbers to AOO420, ready in case of an emergency fix.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

-- 
Mechtilde Stehmann
## Apache OpenOffice.org
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## Loook, calender-exchange-provider, libreoffice-canzeley-client
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature

Re: Issue for 4.1.4 and MacOS

[Dave Fisher]

Hi -

I’ve been trying to get Mac builds going today. I am trying right now with 
trunk. I’m still stuck on configure and have an XCodeLegacy question out to Jim 
on another thread.

checking which jpeg to use... internal
checking which expat to use... internal
checking which libxslt to use... external
checking for xsltproc... /usr/bin/xsltproc
checking which libxml to use... external
checking checking SDK compatibility with OSX 10.9... configure: error: No SDK 
with OSX 10.9 compatibility found
../build_aooreleases.sh: line 153: ./bootstrap: No such file or directory

I have time to try tomorrow.

Regards,
Dave


> On Oct 24, 2017, at 4:06 PM, Patricia Shanahan  wrote:
> 
> Even if you can't get a Mac build going in time to help with this bug, we 
> obviously need more people building and testing on Mac.
> 
> On 10/24/2017 4:01 PM, Peter kovacs wrote:
>> I do own a Mac. But its me. ;) I hope that maybe with the actual guide I can 
>> build. So far I failed to install the old code on it. If I can manage to 
>> build, I could dig into the problem. I have a long weekend upcoming. Hope I 
>> can allocate time.
>> Am 24. Oktober 2017 17:36:16 MESZ schrieb Jim Jagielski :
>>> Will also follow up on the Bugz report, but one change between 4.1.3
>>> and 4.1.4 regarding macOS *builds* is that 4.1.4 uses
>>> '--with-alloc=system'
>>> but the 4.1.3 build does not.
>>> 
>>> I will create a macOS build of AOO414 but adjust the configure script
>>> to not include that and see what effect that may have.
>>> 
>>> 
 On Oct 24, 2017, at 8:52 AM, Patricia Shanahan  wrote:
 
 
 
 On 10/24/2017 5:49 AM, Rory O'Farrell wrote:
> On Tue, 24 Oct 2017 05:35:34 -0700
> Patricia Shanahan  wrote:
>> Since the issue appeared in 4.1.4, and involves document links, it
>>> might
>> be related to my changes.
>> 
>> I do not have a Mac, and do not have any Mac debug experience.
>> 
>> How do people think we should proceed with this? Is there a Mac
>> developer who can work with me on it?
> I don't have access to a Mac, so cannot help there.
> I make one suggestion - a guess - based on loss of images in Writer
>>> (and Calc/Impress? I'm not certain of this) on other operating systems.
> John_Ha has done some work on loss on images in Writer and relates
>>> it to sometimes occurring at the time of OO saving an Autorecovery
>>> image.  See his note at
> https://forum.openoffice.org/en/forum/viewtopic.php?f=71&t=86682
> As this new bug is occurring at Save time, might it be a
>>> manifestation of the same problem?
 
 I don't think there are any changes that relate to that bug between
>>> 4.1.3 and 4.1.4. This seems to be solid and repeatable with 4.1.4, and
>>> not happening at all with 4.1.3.
 
 -
 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
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

[Patricia Shanahan]

Even if you can't get a Mac build going in time to help with this bug, 
we obviously need more people building and testing on Mac.


On 10/24/2017 4:01 PM, Peter kovacs wrote:

I do own a Mac. But its me. ;) I hope that maybe with the actual guide I can 
build. So far I failed to install the old code on it. If I can manage to build, 
I could dig into the problem. I have a long weekend upcoming. Hope I can 
allocate time.

Am 24. Oktober 2017 17:36:16 MESZ schrieb Jim Jagielski :

Will also follow up on the Bugz report, but one change between 4.1.3
and 4.1.4 regarding macOS *builds* is that 4.1.4 uses
'--with-alloc=system'
but the 4.1.3 build does not.

I will create a macOS build of AOO414 but adjust the configure script
to not include that and see what effect that may have.



On Oct 24, 2017, at 8:52 AM, Patricia Shanahan  wrote:



On 10/24/2017 5:49 AM, Rory O'Farrell wrote:

On Tue, 24 Oct 2017 05:35:34 -0700
Patricia Shanahan  wrote:

Since the issue appeared in 4.1.4, and involves document links, it

might

be related to my changes.

I do not have a Mac, and do not have any Mac debug experience.

How do people think we should proceed with this? Is there a Mac
developer who can work with me on it?

I don't have access to a Mac, so cannot help there.
I make one suggestion - a guess - based on loss of images in Writer

(and Calc/Impress? I'm not certain of this) on other operating systems.

John_Ha has done some work on loss on images in Writer and relates

it to sometimes occurring at the time of OO saving an Autorecovery
image.  See his note at

https://forum.openoffice.org/en/forum/viewtopic.php?f=71&t=86682
As this new bug is occurring at Save time, might it be a

manifestation of the same problem?


I don't think there are any changes that relate to that bug between

4.1.3 and 4.1.4. This seems to be solid and repeatable with 4.1.4, and
not happening at all with 4.1.3.


-
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



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Issue for 4.1.4 and MacOS

[Peter kovacs]

I do own a Mac. But its me. ;) I hope that maybe with the actual guide I can 
build. So far I failed to install the old code on it. If I can manage to build, 
I could dig into the problem. I have a long weekend upcoming. Hope I can 
allocate time.

Am 24. Oktober 2017 17:36:16 MESZ schrieb Jim Jagielski :
>Will also follow up on the Bugz report, but one change between 4.1.3
>and 4.1.4 regarding macOS *builds* is that 4.1.4 uses
>'--with-alloc=system'
>but the 4.1.3 build does not.
>
>I will create a macOS build of AOO414 but adjust the configure script
>to not include that and see what effect that may have.
>
>
>> On Oct 24, 2017, at 8:52 AM, Patricia Shanahan  wrote:
>> 
>> 
>> 
>> On 10/24/2017 5:49 AM, Rory O'Farrell wrote:
>>> On Tue, 24 Oct 2017 05:35:34 -0700
>>> Patricia Shanahan  wrote:
 Since the issue appeared in 4.1.4, and involves document links, it
>might
 be related to my changes.
 
 I do not have a Mac, and do not have any Mac debug experience.
 
 How do people think we should proceed with this? Is there a Mac
 developer who can work with me on it?
>>> I don't have access to a Mac, so cannot help there.
>>> I make one suggestion - a guess - based on loss of images in Writer
>(and Calc/Impress? I'm not certain of this) on other operating systems.
>>> John_Ha has done some work on loss on images in Writer and relates
>it to sometimes occurring at the time of OO saving an Autorecovery
>image.  See his note at
>>> https://forum.openoffice.org/en/forum/viewtopic.php?f=71&t=86682
>>> As this new bug is occurring at Save time, might it be a
>manifestation of the same problem?
>> 
>> I don't think there are any changes that relate to that bug between
>4.1.3 and 4.1.4. This seems to be solid and repeatable with 4.1.4, and
>not happening at all with 4.1.3.
>> 
>> -
>> 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: [PROPOSAL] Managing branches for future releases

[Patricia Shanahan]

On 10/24/2017 2:34 PM, Kay Schenk wrote:


On 10/24/2017 01:25 PM, Andrea Pescetti wrote:
I'm starting a short series of occasional posts to capture the current 
collective state of mind on the next release. I'll float them here for 
refinement or lazy consensus, and then we may want to reuse this text 
in wiki or blog posts to avoid repeating the same concepts over and over.


Let's start with branches.

We all wish 4.1.4 to be the last 4.1.x release.

We currently have an AOO415 branch at 
http://svn.apache.org/viewvc/openoffice/branches/AOO415/ ; this branch 
is a copy of AOO414 (that resulted in OpenOffice 4.1.4). The AOO415 
branch will result in a release ONLY if we have some important bug 
fixes to release and trunk is not ready yet. No new features, even 
small enhancements, are added to it. No commits to AOO415 happen 
without appropriate mailing list discussions (dev or security, 
depending on cases).


Trunk is where all development happens. It will be branched for a new 
release (like, an AOO420 branch - name still provisional) when the 
code is mature: beta or even RC. Until then, we simply keep working on 
trunk as we are doing now.


In case we need to commit to a branch, any changes are still committed 
to trunk first and then merged to branches using SVN merge in all 
situations when this is possible (i.e., when there are no merge 
conflicts). The mergeinfo for AOO414 and AOO415 isn't clear, so we'll 
have to make sure that trunk contains all fixes done there (or 
equivalent in case of conflicts) and, done that, we commit to AOO415 
only if:

1. The fix is important and agreed upon on the relevant list
2. The commit is done with "svn merge" starting from a trunk commit

This will ensure that we can shift the focus to trunk while still 
keeping a branch that remains ready for a quick release if needed. If 
we are never in this situation, the next release will be from the 
current trunk and AOO415 will never result in a release.


Regards,
   Andrea.


Would it be more clear to just remove the AOO415 branch and only 
re-instate it if needed (hopefully not). I don't see anything in AOO415 
that wasn't included in AOO414.




The decision to keep the 4.1.5 branch around came out of a discussion on
the security mailing list. The potential problem is that someday we may
be faced with a bug for which we need to get a fix out into the field as
soon as possible.

Because of the sheer size of AOO, it takes time to get set up for a
release. The idea is to do as much as we can to prepare without
committing to a release. I have a check-out of AOO415 built. As the
version number changes get incorporated I'll update and rebuild. Not
having to wait for the branch to be prepared, check it out, and do a
full build reduces by about a day the time it would take from knowing a
fix to having it built, tested, and checked in.

I would like to make this an on-going policy. As soon as we ship 4.2.0,
we remove the AOO415 branch but create AOO421, identical except for
version numbers to AOO420, ready in case of an emergency fix.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [PROPOSAL] Managing branches for future releases

[Andrea Pescetti]

Kay Schenk wrote:

Would it be more clear to just remove the AOO415 branch and only
re-instate it if needed (hopefully not).


No, it wouldn't. See https://bz.apache.org/ooo/show_bug.cgi?id=127552 - 
there is a series of changes that need to be done for the release number 
bump. It's better to have the code ready for it at any moment, so that 
we can really just focus on committing the actual fixes and building in 
case.



I don't see anything in AOO415 that wasn't included in AOO414.


Of course. The two are identical right now. The only fixes that will go 
into the branch are for the release number updates. Anything else will 
go there only after it is fixed in trunk and only after approval on the 
relevant list.


And if trunk is fast enough, we will simply remove the AOO415 branch 
without releasing anything from it.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

[Build] XCodeLegacy - Re: dmake and epm

[Dave Fisher]

Hi Jim,

I’m hung up on what I should do with https://github.com/devernay/xcodelegacy 


What should I download before I run the scripts? Which form of the command 
should I use?

BTW - this requirement is only mentioned in the build release script.

Regards,
Dave

> On Oct 23, 2017, at 5:38 PM, Dave Fisher  wrote:
> 
> Hi Jim,
> 
> I wanted to validate build instructions. Should I take these two from your 
> github for my MacOS Sierra environment?
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On Oct 20, 2017, at 7:31 AM, Jim Jagielski  wrote:
>> 
>> Just a FYI that I am tracking dmake and epm on the
>> below Github pages:
>> 
>>  o https://github.com/jimjag/epm
>>  o https://github.com/jimjag/dmake
>> 
>> I know we are moving away from dmake, but IMO it'll take
>> some time for that to be complete. Plus, updating to the
>> latest version of EPM is useful (it's the ONLY way to build
>> the macOS versions now, for example), but we also need
>> the AOO-specific patches in there. Which are included
>> in my forks.
>> 
>> Just topic for discussion and chewing over
>> 
>> -
>> 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
> 



signature.asc
Description: Message signed with OpenPGP

Re: [PROPOSAL] Managing branches for future releases

[Kay Schenk]

On 10/24/2017 01:25 PM, Andrea Pescetti wrote:
I'm starting a short series of occasional posts to capture the current 
collective state of mind on the next release. I'll float them here for 
refinement or lazy consensus, and then we may want to reuse this text in 
wiki or blog posts to avoid repeating the same concepts over and over.


Let's start with branches.

We all wish 4.1.4 to be the last 4.1.x release.

We currently have an AOO415 branch at 
http://svn.apache.org/viewvc/openoffice/branches/AOO415/ ; this branch 
is a copy of AOO414 (that resulted in OpenOffice 4.1.4). The AOO415 
branch will result in a release ONLY if we have some important bug fixes 
to release and trunk is not ready yet. No new features, even small 
enhancements, are added to it. No commits to AOO415 happen without 
appropriate mailing list discussions (dev or security, depending on cases).


Trunk is where all development happens. It will be branched for a new 
release (like, an AOO420 branch - name still provisional) when the code 
is mature: beta or even RC. Until then, we simply keep working on trunk 
as we are doing now.


In case we need to commit to a branch, any changes are still committed 
to trunk first and then merged to branches using SVN merge in all 
situations when this is possible (i.e., when there are no merge 
conflicts). The mergeinfo for AOO414 and AOO415 isn't clear, so we'll 
have to make sure that trunk contains all fixes done there (or 
equivalent in case of conflicts) and, done that, we commit to AOO415 
only if:

1. The fix is important and agreed upon on the relevant list
2. The commit is done with "svn merge" starting from a trunk commit

This will ensure that we can shift the focus to trunk while still 
keeping a branch that remains ready for a quick release if needed. If we 
are never in this situation, the next release will be from the current 
trunk and AOO415 will never result in a release.


Regards,
   Andrea.


Would it be more clear to just remove the AOO415 branch and only 
re-instate it if needed (hopefully not). I don't see anything in AOO415 
that wasn't included in AOO414.


--
--
MzK

"Only the truth will save you now."
  -- Ensei Tankado, "Digital Fortress"

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

[PROPOSAL] Managing branches for future releases

[Andrea Pescetti]

I'm starting a short series of occasional posts to capture the current 
collective state of mind on the next release. I'll float them here for 
refinement or lazy consensus, and then we may want to reuse this text in 
wiki or blog posts to avoid repeating the same concepts over and over.


Let's start with branches.

We all wish 4.1.4 to be the last 4.1.x release.

We currently have an AOO415 branch at 
http://svn.apache.org/viewvc/openoffice/branches/AOO415/ ; this branch 
is a copy of AOO414 (that resulted in OpenOffice 4.1.4). The AOO415 
branch will result in a release ONLY if we have some important bug fixes 
to release and trunk is not ready yet. No new features, even small 
enhancements, are added to it. No commits to AOO415 happen without 
appropriate mailing list discussions (dev or security, depending on cases).


Trunk is where all development happens. It will be branched for a new 
release (like, an AOO420 branch - name still provisional) when the code 
is mature: beta or even RC. Until then, we simply keep working on trunk 
as we are doing now.


In case we need to commit to a branch, any changes are still committed 
to trunk first and then merged to branches using SVN merge in all 
situations when this is possible (i.e., when there are no merge 
conflicts). The mergeinfo for AOO414 and AOO415 isn't clear, so we'll 
have to make sure that trunk contains all fixes done there (or 
equivalent in case of conflicts) and, done that, we commit to AOO415 
only if:

1. The fix is important and agreed upon on the relevant list
2. The commit is done with "svn merge" starting from a trunk commit

This will ensure that we can shift the focus to trunk while still 
keeping a branch that remains ready for a quick release if needed. If we 
are never in this situation, the next release will be from the current 
trunk and AOO415 will never result in a release.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: QA Improvements on 4.2.0

[Dave Fisher]

Hi -

I agree and wrote the same on a different thread the other day.

Regards,
Dave

> On Oct 24, 2017, at 3:28 AM, Pedro Lino  wrote:
> 
> Hi Raphael, all
> 
>> I believe the 4.1.4 shows us, that we have to do a better job in QA. A
>> minor release should never go to a rc5. I believe we all (and I pointing
>> my finger to myself) underestimated the regression risk at the 4.1.4.
> 
> +1
> 
>> So, to do a better job in the 4.2.0 I propose the following changes.
>> 
>> - Define test areas, where tester should keep an extra eye on it. (based
>> on the changes)
>> - Doing Developer Snapshots again in a 2 Week frequency (or so)
>> - Switch the AOO Profile for the snapshots to AOO-Dev
>> - mobilize the willing testers to keep a critical eye on this builds
>> - maybe also run the automated tests for Apache OpenOffice.
> 
> As a user/tester/part-timeQA I agree to all points.
> 
> But, please include Language packs in Developer Snapshots. Running a build 
> with an un-matching language pack causes very serious usability problems 
> (this is IMO the only advantage of including all languages in a single 
> installer).
> 
> Creating a blank AOO-Dev profile is a two edged sword: you get a clean start 
> (and avoid trashing the user's work profile) but it isn't a realistic usage 
> (and therefore testing will not find those day to day problems that resulted 
> in the need to go to RC5)
> Maybe a middle term would be to create a separate Dev profile that is a copy 
> of the user's profile (including all extensions)?
> 
>> The idea is to make the bug cycle shorter. Improvements should be tested
>> right after the implementation and not short before the release. A fresh
>> bug is easier to fix as a old one.
> 
> That is the ideal situation. But requires more communication (the QA mailing 
> list is unused for months) and especially more man power (on all platforms!). 
> The only way to get more users is to add needed/missing features and get 
> visibility...
> 
> Regards,
> Pedro
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: Issue for 4.1.4 and MacOS

[Jim Jagielski]

Will also follow up on the Bugz report, but one change between 4.1.3
and 4.1.4 regarding macOS *builds* is that 4.1.4 uses '--with-alloc=system'
but the 4.1.3 build does not.

I will create a macOS build of AOO414 but adjust the configure script
to not include that and see what effect that may have.


> On Oct 24, 2017, at 8:52 AM, Patricia Shanahan  wrote:
> 
> 
> 
> On 10/24/2017 5:49 AM, Rory O'Farrell wrote:
>> On Tue, 24 Oct 2017 05:35:34 -0700
>> Patricia Shanahan  wrote:
>>> Since the issue appeared in 4.1.4, and involves document links, it might
>>> be related to my changes.
>>> 
>>> I do not have a Mac, and do not have any Mac debug experience.
>>> 
>>> How do people think we should proceed with this? Is there a Mac
>>> developer who can work with me on it?
>> I don't have access to a Mac, so cannot help there.
>> I make one suggestion - a guess - based on loss of images in Writer (and 
>> Calc/Impress? I'm not certain of this) on other operating systems.
>> John_Ha has done some work on loss on images in Writer and relates it to 
>> sometimes occurring at the time of OO saving an Autorecovery image.  See his 
>> note at
>> https://forum.openoffice.org/en/forum/viewtopic.php?f=71&t=86682
>> As this new bug is occurring at Save time, might it be a manifestation of 
>> the same problem?
> 
> I don't think there are any changes that relate to that bug between 4.1.3 and 
> 4.1.4. This seems to be solid and repeatable with 4.1.4, and not happening at 
> all with 4.1.3.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> 
> For additional commands, e-mail: dev-h...@openoffice.apache.org 
> 

Re: Issue for 4.1.4 and MacOS

[Patricia Shanahan]

On 10/24/2017 5:49 AM, Rory O'Farrell wrote:

On Tue, 24 Oct 2017 05:35:34 -0700
Patricia Shanahan  wrote:


Since the issue appeared in 4.1.4, and involves document links, it might
be related to my changes.

I do not have a Mac, and do not have any Mac debug experience.

How do people think we should proceed with this? Is there a Mac
developer who can work with me on it?


I don't have access to a Mac, so cannot help there.

I make one suggestion - a guess - based on loss of images in Writer (and 
Calc/Impress? I'm not certain of this) on other operating systems.

John_Ha has done some work on loss on images in Writer and relates it to 
sometimes occurring at the time of OO saving an Autorecovery image.  See his 
note at
https://forum.openoffice.org/en/forum/viewtopic.php?f=71&t=86682

As this new bug is occurring at Save time, might it be a manifestation of the 
same problem?



I don't think there are any changes that relate to that bug between 
4.1.3 and 4.1.4. This seems to be solid and repeatable with 4.1.4, and 
not happening at all with 4.1.3.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Issue for 4.1.4 and MacOS

[Rory O'Farrell]

On Tue, 24 Oct 2017 05:35:34 -0700
Patricia Shanahan  wrote:

> Since the issue appeared in 4.1.4, and involves document links, it might 
> be related to my changes.
> 
> I do not have a Mac, and do not have any Mac debug experience.
> 
> How do people think we should proceed with this? Is there a Mac 
> developer who can work with me on it?

I don't have access to a Mac, so cannot help there.  

I make one suggestion - a guess - based on loss of images in Writer (and 
Calc/Impress? I'm not certain of this) on other operating systems.  

John_Ha has done some work on loss on images in Writer and relates it to 
sometimes occurring at the time of OO saving an Autorecovery image.  See his 
note at
https://forum.openoffice.org/en/forum/viewtopic.php?f=71&t=86682

As this new bug is occurring at Save time, might it be a manifestation of the 
same problem?

Rory


> 
> On 10/24/2017 4:40 AM, Larry Gusaas wrote:
> > On 2017-10-24, 4:19 AM FR web forum wrote:
> > 
> >> Please have a look on:
> >> https://bz.apache.org/ooo/show_bug.cgi?id=127568
> > 
> > I tested and confirm the problem. Posted my result on the bug report.
> > 
> > 
> 
> -
> 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: Issue for 4.1.4 and MacOS

[Patricia Shanahan]

Since the issue appeared in 4.1.4, and involves document links, it might 
be related to my changes.


I do not have a Mac, and do not have any Mac debug experience.

How do people think we should proceed with this? Is there a Mac 
developer who can work with me on it?


On 10/24/2017 4:40 AM, Larry Gusaas wrote:

On 2017-10-24, 4:19 AM FR web forum wrote:


Please have a look on:
https://bz.apache.org/ooo/show_bug.cgi?id=127568


I tested and confirm the problem. Posted my result on the bug report.




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Issue for 4.1.4 and MacOS

[Larry Gusaas]

On 2017-10-24, 4:19 AM FR web forum wrote:


Please have a look on:
https://bz.apache.org/ooo/show_bug.cgi?id=127568


I tested and confirm the problem. Posted my result on the bug report.


--
_

Larry I. Gusaas
Moose Jaw, Saskatchewan Canada
Website: http://larry-gusaas.com
"An artist is never ahead of his time but most people are far behind theirs." - 
Edgard Varese



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: QA Improvements on 4.2.0

[Pedro Lino]

Hi Raphael, all

> I believe the 4.1.4 shows us, that we have to do a better job in QA. A  
> minor release should never go to a rc5. I believe we all (and I pointing  
> my finger to myself) underestimated the regression risk at the 4.1.4.

+1

> So, to do a better job in the 4.2.0 I propose the following changes.
> 
> - Define test areas, where tester should keep an extra eye on it. (based  
> on the changes)
> - Doing Developer Snapshots again in a 2 Week frequency (or so)
> - Switch the AOO Profile for the snapshots to AOO-Dev
> - mobilize the willing testers to keep a critical eye on this builds
> - maybe also run the automated tests for Apache OpenOffice.

As a user/tester/part-timeQA I agree to all points.

But, please include Language packs in Developer Snapshots. Running a build with 
an un-matching language pack causes very serious usability problems (this is 
IMO the only advantage of including all languages in a single installer).

Creating a blank AOO-Dev profile is a two edged sword: you get a clean start 
(and avoid trashing the user's work profile) but it isn't a realistic usage 
(and therefore testing will not find those day to day problems that resulted in 
the need to go to RC5)
Maybe a middle term would be to create a separate Dev profile that is a copy of 
the user's profile (including all extensions)?

> The idea is to make the bug cycle shorter. Improvements should be tested  
> right after the implementation and not short before the release. A fresh  
> bug is easier to fix as a old one.

That is the ideal situation. But requires more communication (the QA mailing 
list is unused for months) and especially more man power (on all platforms!). 
The only way to get more users is to add needed/missing features and get 
visibility...

Regards,
Pedro

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Issue for 4.1.4 and MacOS

[FR web forum]

Please have a look on:
https://bz.apache.org/ooo/show_bug.cgi?id=127568

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Tajik hunspell dictionary

[Andrea Pescetti]

Odil Soliev wrote:

We are prepare a Tajik hunspell dictionary for OpenOffice. How  can we add our 
dictionary to OpenOffice distribution?


After you are done with the dictionary (.dic and .aff files), package 
them into an extension and upload it to http://extensions.openoffice.org/


You can use the Italian dictionary 
https://extensions.openoffice.org/node/1204 as a reference (just 
download the oxt file and unzip it).


If you have any other questions, just ask here on the dev list.

Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org