Re: [Build] XCode 8.3.3 / 4.1.4 - quicktime.h header missing

2017-10-26 Thread Dave Fisher
Downloading the SDK now.

While I wait - I run from terminal are you running elsewhere?

> On Oct 26, 2017, at 4:59 PM, Jim Jagielski  wrote:
> 
> sdk 10.9 lacks Python. No idea why.
> 
> Install sdk 10.11 and configure should find and use that one.
> 
> All this is fixed in trunk.
> 
>> On Oct 26, 2017, at 7:29 PM, Dave Fisher > > wrote:
>> 
>> Hi -
>> 
>> Well this is a royal pain to setup.
>> 
>> I’ve done the xcodelegacy and have installed the 10.7 and 10.9 SDKs.
>> 
>> I have a fresh copy of the branch AOO414. I run and now it cannot find 
>> python headers.
>> 
>> checking which python to use... compiling against system python 
>> (/usr/bin/python)
>> compiling against system python (version 2.7)
>> checking Python.h usability... no
>> checking Python.h presence... no
>> checking for Python.h... no
>> configure: error: Python headers not found
>> 
>> I need help. What the heck happened to my Python setup?
>> 
>> Thanks,
>> Dave
>> 
>>> On Oct 26, 2017, at 1:00 PM, Dave Fisher >> >> >> wrote:
>>> 
>>> Hi Jim,
>>> 
>>> I’m building AOO 4.1.4 using macOS12 library and made it all the way to VCL 
>>> where I get:
>>> 
>>> /Users/davewave/Development/aoo-4.1.4/main/vcl/aqua/source/dtrans/PictToBmpFlt.cxx:34:10:
>>>  fatal error: 'QuickTime/QuickTime.h' file not found
>>> #include 
>>> 
>>> Do I need to use XCodeLegacy and point to 10.7?
>>> 
>>> Regards,
>>> Dave
>>> 
 On Oct 25, 2017, at 12:24 PM, Dave Fisher >> wrote:
 
 Hi -
 
 I am now on Xcode 8.3.3. Cleaned up and reset.
 
 I now I’m on an issues with Redland:
 
 configure: error: Raptor  is too old - see http://librdf.org/raptor/ 
  > to get a 2.0.7 or newer
 dmake:  Error code 1, while making 
 '../unxmaccx.pro/misc/build/so_configured_so_rasqal'
 
 1 module(s):
redland
 need(s) to be rebuilt
 
 Reason(s):
 
 ERROR: error 65280 occurred while making 
 /Users/davewave/Development/aoo/main/redland/rasqal
 
 When you have fixed the errors in that module you can resume the build by 
 running:
 
build --all:redland
 
 Looking into this it looks bogus and I went past the check and now:
 
 configure: error: Rasqal is not installed or too old - see 
 http://librdf.org/rasqal/ 
 > to get a version in range 0.9.25 to 0.9.99
 dmake:  Error code 1, while making 
 '../unxmaccx.pro/misc/build/so_configured_so_redland'
 
 1 module(s):
redland
 need(s) to be rebuilt
 
 Reason(s):
 
 ERROR: error 65280 occurred while making 
 /Users/davewave/Development/aoo/main/redland/redland
 
 When you have fixed the errors in that module you can resume the build by 
 running:
 
build --all:redland
 
 Looks like I have something off in my environment.
 
 Regards,
 Dave
 
 
> On Oct 25, 2017, at 8:19 AM, Dave Fisher   >> wrote:
> 
> Hi Jim,
> 
> Thanks. I have Xcode 9 which has the following:
> 
> $ xcodebuild -showsdks
> iOS SDKs:
>   iOS 11.0-sdk iphoneos11.0
> 
> iOS Simulator SDKs:
>   Simulator - iOS 11.0-sdk iphonesimulator11.0
> 
> macOS SDKs:
>   macOS 10.13 -sdk macosx10.13
> 
> tvOS SDKs:
>   tvOS 11.0   -sdk appletvos11.0
> 
> tvOS Simulator SDKs:
>   Simulator - tvOS 11.0   -sdk appletvsimulator11.0
> 
> watchOS SDKs:
>   watchOS 4.0 -sdk watchos4.0
> 
> watchOS Simulator SDKs:
>   Simulator - watchOS 4.0 -sdk watchsimulator4.0
> 
> I modified configure to target 10.13 and adjusted the egrep:
> 
> sdk_found=`xcodebuild -showsdks | $EGREP "sdk macosx10.(10|11|12|13)" | 
> sed -e "s/.*sdk //" | head -n1`
> 
> Also -
> #   sdk_target=10.9
>   sdk_target=10.13
> 
> The last means the environment variable MACOSX_DEPLOYMENT_TARGET in the 
> release script is not used.
> 
> On to the next issue with the category B downloads. Certificate store 
> issues giving 500 errors.
> 
> Also, I noticed a version 5.5 of Tomcat ….
> 
> Regards,
> Dave
> 
>> On Oct 25, 2017, at 5:32 AM, Jim Jagielski > 

Re: [Build] XCode 8.3.3 / 4.1.4 - quicktime.h header missing

2017-10-26 Thread Jim Jagielski
sdk 10.9 lacks Python. No idea why.

Install sdk 10.11 and configure should find and use that one.

All this is fixed in trunk.

> On Oct 26, 2017, at 7:29 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> Well this is a royal pain to setup.
> 
> I’ve done the xcodelegacy and have installed the 10.7 and 10.9 SDKs.
> 
> I have a fresh copy of the branch AOO414. I run and now it cannot find python 
> headers.
> 
> checking which python to use... compiling against system python 
> (/usr/bin/python)
> compiling against system python (version 2.7)
> checking Python.h usability... no
> checking Python.h presence... no
> checking for Python.h... no
> configure: error: Python headers not found
> 
> I need help. What the heck happened to my Python setup?
> 
> Thanks,
> Dave
> 
>> On Oct 26, 2017, at 1:00 PM, Dave Fisher > > wrote:
>> 
>> Hi Jim,
>> 
>> I’m building AOO 4.1.4 using macOS12 library and made it all the way to VCL 
>> where I get:
>> 
>> /Users/davewave/Development/aoo-4.1.4/main/vcl/aqua/source/dtrans/PictToBmpFlt.cxx:34:10:
>>  fatal error: 'QuickTime/QuickTime.h' file not found
>> #include 
>> 
>> Do I need to use XCodeLegacy and point to 10.7?
>> 
>> Regards,
>> Dave
>> 
>>> On Oct 25, 2017, at 12:24 PM, Dave Fisher >> > wrote:
>>> 
>>> Hi -
>>> 
>>> I am now on Xcode 8.3.3. Cleaned up and reset.
>>> 
>>> I now I’m on an issues with Redland:
>>> 
>>> configure: error: Raptor  is too old - see http://librdf.org/raptor/ 
>>>  to get a 2.0.7 or newer
>>> dmake:  Error code 1, while making 
>>> '../unxmaccx.pro/misc/build/so_configured_so_rasqal'
>>> 
>>> 1 module(s): 
>>> redland
>>> need(s) to be rebuilt
>>> 
>>> Reason(s):
>>> 
>>> ERROR: error 65280 occurred while making 
>>> /Users/davewave/Development/aoo/main/redland/rasqal
>>> 
>>> When you have fixed the errors in that module you can resume the build by 
>>> running:
>>> 
>>> build --all:redland
>>> 
>>> Looking into this it looks bogus and I went past the check and now:
>>> 
>>> configure: error: Rasqal is not installed or too old - see 
>>> http://librdf.org/rasqal/  to get a version in 
>>> range 0.9.25 to 0.9.99
>>> dmake:  Error code 1, while making 
>>> '../unxmaccx.pro/misc/build/so_configured_so_redland'
>>> 
>>> 1 module(s): 
>>> redland
>>> need(s) to be rebuilt
>>> 
>>> Reason(s):
>>> 
>>> ERROR: error 65280 occurred while making 
>>> /Users/davewave/Development/aoo/main/redland/redland
>>> 
>>> When you have fixed the errors in that module you can resume the build by 
>>> running:
>>> 
>>> build --all:redland
>>> 
>>> Looks like I have something off in my environment.
>>> 
>>> Regards,
>>> Dave
>>> 
>>> 
 On Oct 25, 2017, at 8:19 AM, Dave Fisher > wrote:
 
 Hi Jim,
 
 Thanks. I have Xcode 9 which has the following:
 
 $ xcodebuild -showsdks
 iOS SDKs:
iOS 11.0-sdk iphoneos11.0
 
 iOS Simulator SDKs:
Simulator - iOS 11.0-sdk iphonesimulator11.0
 
 macOS SDKs:
macOS 10.13 -sdk macosx10.13
 
 tvOS SDKs:
tvOS 11.0   -sdk appletvos11.0
 
 tvOS Simulator SDKs:
Simulator - tvOS 11.0   -sdk appletvsimulator11.0
 
 watchOS SDKs:
watchOS 4.0 -sdk watchos4.0
 
 watchOS Simulator SDKs:
Simulator - watchOS 4.0 -sdk watchsimulator4.0
 
 I modified configure to target 10.13 and adjusted the egrep:
 
 sdk_found=`xcodebuild -showsdks | $EGREP "sdk macosx10.(10|11|12|13)" | 
 sed -e "s/.*sdk //" | head -n1`
 
 Also - 
 #   sdk_target=10.9

 
sdk_target=10.13
 
 The last means the environment variable MACOSX_DEPLOYMENT_TARGET in the 
 release script is not used.
 
 On to the next issue with the category B downloads. Certificate store 
 issues giving 500 errors.
 
 Also, I noticed a version 5.5 of Tomcat ….
 
 Regards,
 Dave
 
> On Oct 25, 2017, at 5:32 AM, Jim Jagielski  > wrote:
> 
> Actually, if you have Xcode7 or Xcode8, there is no need for
> Xcodelegacy at all.
> 
> All Xcodelegacy does is obtain older macOS SDKs and installs them
> in Xcode. But we use the latest SDK available (via configure). So
> Xcodelegacy is not a requirement/dependency per se. It's just
> useful in case we get into a situation where we need to
> use an older SDK rather than the latest.
> 
>> On Oct 24, 2017, at 6:00 PM, Dave Fisher 

Re: [Build] XCode 8.3.3 / 4.1.4 - quicktime.h header missing

2017-10-26 Thread Dave Fisher
Hi -

Well this is a royal pain to setup.

I’ve done the xcodelegacy and have installed the 10.7 and 10.9 SDKs.

I have a fresh copy of the branch AOO414. I run and now it cannot find python 
headers.

checking which python to use... compiling against system python 
(/usr/bin/python)
compiling against system python (version 2.7)
checking Python.h usability... no
checking Python.h presence... no
checking for Python.h... no
configure: error: Python headers not found

I need help. What the heck happened to my Python setup?

Thanks,
Dave

> On Oct 26, 2017, at 1:00 PM, Dave Fisher  wrote:
> 
> Hi Jim,
> 
> I’m building AOO 4.1.4 using macOS12 library and made it all the way to VCL 
> where I get:
> 
> /Users/davewave/Development/aoo-4.1.4/main/vcl/aqua/source/dtrans/PictToBmpFlt.cxx:34:10:
>  fatal error: 'QuickTime/QuickTime.h' file not found
> #include 
> 
> Do I need to use XCodeLegacy and point to 10.7?
> 
> Regards,
> Dave
> 
>> On Oct 25, 2017, at 12:24 PM, Dave Fisher > > wrote:
>> 
>> Hi -
>> 
>> I am now on Xcode 8.3.3. Cleaned up and reset.
>> 
>> I now I’m on an issues with Redland:
>> 
>> configure: error: Raptor  is too old - see http://librdf.org/raptor/ 
>>  to get a 2.0.7 or newer
>> dmake:  Error code 1, while making 
>> '../unxmaccx.pro/misc/build/so_configured_so_rasqal'
>> 
>> 1 module(s):
>>  redland
>> need(s) to be rebuilt
>> 
>> Reason(s):
>> 
>> ERROR: error 65280 occurred while making 
>> /Users/davewave/Development/aoo/main/redland/rasqal
>> 
>> When you have fixed the errors in that module you can resume the build by 
>> running:
>> 
>>  build --all:redland
>> 
>> Looking into this it looks bogus and I went past the check and now:
>> 
>> configure: error: Rasqal is not installed or too old - see 
>> http://librdf.org/rasqal/  to get a version in 
>> range 0.9.25 to 0.9.99
>> dmake:  Error code 1, while making 
>> '../unxmaccx.pro/misc/build/so_configured_so_redland'
>> 
>> 1 module(s):
>>  redland
>> need(s) to be rebuilt
>> 
>> Reason(s):
>> 
>> ERROR: error 65280 occurred while making 
>> /Users/davewave/Development/aoo/main/redland/redland
>> 
>> When you have fixed the errors in that module you can resume the build by 
>> running:
>> 
>>  build --all:redland
>> 
>> Looks like I have something off in my environment.
>> 
>> Regards,
>> Dave
>> 
>> 
>>> On Oct 25, 2017, at 8:19 AM, Dave Fisher >> > wrote:
>>> 
>>> Hi Jim,
>>> 
>>> Thanks. I have Xcode 9 which has the following:
>>> 
>>> $ xcodebuild -showsdks
>>> iOS SDKs:
>>> iOS 11.0-sdk iphoneos11.0
>>> 
>>> iOS Simulator SDKs:
>>> Simulator - iOS 11.0-sdk iphonesimulator11.0
>>> 
>>> macOS SDKs:
>>> macOS 10.13 -sdk macosx10.13
>>> 
>>> tvOS SDKs:
>>> tvOS 11.0   -sdk appletvos11.0
>>> 
>>> tvOS Simulator SDKs:
>>> Simulator - tvOS 11.0   -sdk appletvsimulator11.0
>>> 
>>> watchOS SDKs:
>>> watchOS 4.0 -sdk watchos4.0
>>> 
>>> watchOS Simulator SDKs:
>>> Simulator - watchOS 4.0 -sdk watchsimulator4.0
>>> 
>>> I modified configure to target 10.13 and adjusted the egrep:
>>> 
>>> sdk_found=`xcodebuild -showsdks | $EGREP "sdk macosx10.(10|11|12|13)" | sed 
>>> -e "s/.*sdk //" | head -n1`
>>> 
>>> Also -
>>> #   sdk_target=10.9
>>>sdk_target=10.13
>>> 
>>> The last means the environment variable MACOSX_DEPLOYMENT_TARGET in the 
>>> release script is not used.
>>> 
>>> On to the next issue with the category B downloads. Certificate store 
>>> issues giving 500 errors.
>>> 
>>> Also, I noticed a version 5.5 of Tomcat ….
>>> 
>>> Regards,
>>> Dave
>>> 
 On Oct 25, 2017, at 5:32 AM, Jim Jagielski > wrote:
 
 Actually, if you have Xcode7 or Xcode8, there is no need for
 Xcodelegacy at all.
 
 All Xcodelegacy does is obtain older macOS SDKs and installs them
 in Xcode. But we use the latest SDK available (via configure). So
 Xcodelegacy is not a requirement/dependency per se. It's just
 useful in case we get into a situation where we need to
 use an older SDK rather than the latest.
 
> On Oct 24, 2017, at 6:00 PM, Dave Fisher  > wrote:
> 
> 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, 

Update Re: Java 9 on macOS

2017-10-26 Thread Larry Gusaas
Apache OpenOffice 4.1.4 now recognizes Java 9 (jdk-9.0.1.jdk). The Apple legacy Java 6 is no 
longer required (I deleted it from my system.

AOO database works with new Java.

Sorry for the typos in AOO versions in my previous post.

Larry


--
_

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: Access denied on Dictionaries page

2017-10-26 Thread Marcus

Am 26.10.2017 um 23:24 schrieb Andrea Pescetti:

Marcus wrote:

Am 26.10.2017 um 22:23 schrieb Andrea Pescetti:

If we see users confused by the "double update" process we will have
to add an item to the Release Notes.

I don't understand what you want to write to the release notes.


I mean: if we start getting e-mails from people who say "I upgraded to 
version 4.1.4 and the upgrade failed since it still tells me that an 
update is available" then we should explain somewhere that the 
application updates and the dictionary updates are separate, and that it 
is expected that after upgrading to 4.1.4 you are notified that a newer 
English dictionary is available. If users actually read and understand 
messages, there will be no need for this.


I think the most people don't read them and don't know that such is 
existing at all. So, we can add something to the relase notes but IMHO 
this won't change anything.


Marcus


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



Re: Access denied on Dictionaries page

2017-10-26 Thread Andrea Pescetti

Marcus wrote:

Am 26.10.2017 um 22:23 schrieb Andrea Pescetti:

If we see users confused by the "double update" process we will have
to add an item to the Release Notes.

I don't understand what you want to write to the release notes.


I mean: if we start getting e-mails from people who say "I upgraded to 
version 4.1.4 and the upgrade failed since it still tells me that an 
update is available" then we should explain somewhere that the 
application updates and the dictionary updates are separate, and that it 
is expected that after upgrading to 4.1.4 you are notified that a newer 
English dictionary is available. If users actually read and understand 
messages, there will be no need for this.


Regards,
  Andrea.

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



Re: Access denied on Dictionaries page

2017-10-26 Thread Marcus

Am 26.10.2017 um 22:23 schrieb Andrea Pescetti:

On 26/10/2017 Marcus wrote:

Am 26.10.2017 um 12:09 schrieb Marco A.G.Pinto:

Now I get an access error in the official page:
http://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice 



maybe a temporary outage in the second where you have looked.
I've test now and it's working.


Besides the problem itself (I confirm I see the page normally too) this 
means that people who upgrade to OpenOffice 4.1.4 will immediately see a 
notice saying they should update their English dictionary.


This is quite annoying but there is nothing we can do about it right now.

For the next version we should probably, like we did in the past, agree 
that the English dictionary does not get updated for at least one month 
after release.


we could write to the usual mailing lists to ask for a 1 month break of 
updates. I'm pretty sure that Marco would support us. But others we 
don't know and when they don't write about their updates here, we won't 
reach.


If we see users confused by the "double update" process we will have to 
add an item to the Release Notes.

I don't understand what you want to write to the release notes.

Marcus

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



Post-release steps for 4.1.4

2017-10-26 Thread Andrea Pescetti
A short summary of the post-release steps for 4.1.4 I'm going to take 
care of, since we are now at the "7 days after release" mark:


1) Security reports for 4.1.4 are now published at
https://www.openoffice.org/security/bulletin.html
Nothing special, the usual handful of fixes we do at every release; but 
I'll now send a notice to the announce@ list with this link.


2) Update feeds haven't been updated yet. They are organized by language 
and version (i.e., there is a feed that will be shown to current users 
of version 4.1.3 in Italian, one for version 4.1.2 in French, one for 
4.1.2 in German, one for 4.1.1 in German...), so a lot of combinations.


I plan to:
- Enable feeds for 4.1.3 in French, German, Italian (three random 
"medium-size" languages) within the next 24 hours.
- 24/48 hours later, enable feeds for 4.1.3 in all other languages 
including English

- As time allows, enable feeds for users of versions < 4.1.3

Regards,
  Andrea.

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



Re: Access denied on Dictionaries page

2017-10-26 Thread Andrea Pescetti

On 26/10/2017 Marcus wrote:

Am 26.10.2017 um 12:09 schrieb Marco A.G.Pinto:

Now I get an access error in the official page:
http://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice


maybe a temporary outage in the second where you have looked.
I've test now and it's working.


Besides the problem itself (I confirm I see the page normally too) this 
means that people who upgrade to OpenOffice 4.1.4 will immediately see a 
notice saying they should update their English dictionary.


This is quite annoying but there is nothing we can do about it right now.

For the next version we should probably, like we did in the past, agree 
that the English dictionary does not get updated for at least one month 
after release.


If we see users confused by the "double update" process we will have to 
add an item to the Release Notes.


Regards,
  Andrea.

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



Re: [Build] XCode 8.3.3 / 4.1.4 - quicktime.h header missing

2017-10-26 Thread Dave Fisher
Hi Jim,

I’m building AOO 4.1.4 using macOS12 library and made it all the way to VCL 
where I get:

/Users/davewave/Development/aoo-4.1.4/main/vcl/aqua/source/dtrans/PictToBmpFlt.cxx:34:10:
 fatal error: 'QuickTime/QuickTime.h' file not found
#include 

Do I need to use XCodeLegacy and point to 10.7?

Regards,
Dave

> On Oct 25, 2017, at 12:24 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> I am now on Xcode 8.3.3. Cleaned up and reset.
> 
> I now I’m on an issues with Redland:
> 
> configure: error: Raptor  is too old - see http://librdf.org/raptor/ 
>  to get a 2.0.7 or newer
> dmake:  Error code 1, while making 
> '../unxmaccx.pro/misc/build/so_configured_so_rasqal'
> 
> 1 module(s):
>   redland
> need(s) to be rebuilt
> 
> Reason(s):
> 
> ERROR: error 65280 occurred while making 
> /Users/davewave/Development/aoo/main/redland/rasqal
> 
> When you have fixed the errors in that module you can resume the build by 
> running:
> 
>   build --all:redland
> 
> Looking into this it looks bogus and I went past the check and now:
> 
> configure: error: Rasqal is not installed or too old - see 
> http://librdf.org/rasqal/  to get a version in 
> range 0.9.25 to 0.9.99
> dmake:  Error code 1, while making 
> '../unxmaccx.pro/misc/build/so_configured_so_redland'
> 
> 1 module(s):
>   redland
> need(s) to be rebuilt
> 
> Reason(s):
> 
> ERROR: error 65280 occurred while making 
> /Users/davewave/Development/aoo/main/redland/redland
> 
> When you have fixed the errors in that module you can resume the build by 
> running:
> 
>   build --all:redland
> 
> Looks like I have something off in my environment.
> 
> Regards,
> Dave
> 
> 
>> On Oct 25, 2017, at 8:19 AM, Dave Fisher > > wrote:
>> 
>> Hi Jim,
>> 
>> Thanks. I have Xcode 9 which has the following:
>> 
>> $ xcodebuild -showsdks
>> iOS SDKs:
>>  iOS 11.0-sdk iphoneos11.0
>> 
>> iOS Simulator SDKs:
>>  Simulator - iOS 11.0-sdk iphonesimulator11.0
>> 
>> macOS SDKs:
>>  macOS 10.13 -sdk macosx10.13
>> 
>> tvOS SDKs:
>>  tvOS 11.0   -sdk appletvos11.0
>> 
>> tvOS Simulator SDKs:
>>  Simulator - tvOS 11.0   -sdk appletvsimulator11.0
>> 
>> watchOS SDKs:
>>  watchOS 4.0 -sdk watchos4.0
>> 
>> watchOS Simulator SDKs:
>>  Simulator - watchOS 4.0 -sdk watchsimulator4.0
>> 
>> I modified configure to target 10.13 and adjusted the egrep:
>> 
>> sdk_found=`xcodebuild -showsdks | $EGREP "sdk macosx10.(10|11|12|13)" | sed 
>> -e "s/.*sdk //" | head -n1`
>> 
>> Also -
>> #   sdk_target=10.9
>>sdk_target=10.13
>> 
>> The last means the environment variable MACOSX_DEPLOYMENT_TARGET in the 
>> release script is not used.
>> 
>> On to the next issue with the category B downloads. Certificate store issues 
>> giving 500 errors.
>> 
>> Also, I noticed a version 5.5 of Tomcat ….
>> 
>> Regards,
>> Dave
>> 
>>> On Oct 25, 2017, at 5:32 AM, Jim Jagielski >> > wrote:
>>> 
>>> Actually, if you have Xcode7 or Xcode8, there is no need for
>>> Xcodelegacy at all.
>>> 
>>> All Xcodelegacy does is obtain older macOS SDKs and installs them
>>> in Xcode. But we use the latest SDK available (via configure). So
>>> Xcodelegacy is not a requirement/dependency per se. It's just
>>> useful in case we get into a situation where we need to
>>> use an older SDK rather than the latest.
>>> 
 On Oct 24, 2017, at 6:00 PM, Dave Fisher > wrote:
 
 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  
>> 

Re: Was können wir gegen Trittbrettfahrer tun?

2017-10-26 Thread Jörg Schmidt
Hallo Dave, 

> > Vielleicht vorerst die Betreiber dieser Seite um eine offizielle
> Stellungnahme bitten? 

Ich wiederhole mich das die von mir genannte Seite ein Beispiel war und nicht 
unbedingt die Seite von der sich der Anwender betrogen fühlt, denn die hat er 
nicht genannt.

Ich weiß jedoch eines, die von mir genannte Seite reagiert auf Email-Anfragen 
nicht, denn ich selbst hatte dort schon einmal angefragt und jüngst schrieb 
irgendwer (bei uns im Forum? oder anderswo) das auch er angefragt hätte und 
keine Antwort bekam.

Nach meiner Einschätzung dürfte der Betreiber wissen das seine Situation 
juristisch wasserdicht ist und er reagiert nicht um sich überhaupt erst nicht 
auf Wortgefechte einzulassen.



Gruß
Jörg


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



Re: Access denied on Dictionaries page

2017-10-26 Thread Rory O'Farrell
On Thu, 26 Oct 2017 21:07:32 +0200
Marcus  wrote:

> Am 26.10.2017 um 12:09 schrieb Marco A.G.Pinto:
> 
> Hi Marco,
> 
> > Now I get an access error in the official page:
> > http://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice
> > 
> > Could someone take a look at it?
> 
> maybe a temporary outage in the second where you have looked.
> I've test now and it's working.
> 
> Marcus
> 

It downloaded and installed correctly for me just now.

-- 
Rory O'Farrell 

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



Re: Access denied on Dictionaries page

2017-10-26 Thread Marcus

Am 26.10.2017 um 12:09 schrieb Marco A.G.Pinto:

Hi Marco,


Now I get an access error in the official page:
http://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice

Could someone take a look at it?


maybe a temporary outage in the second where you have looked.
I've test now and it's working.

Marcus


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



Re: Was können wir gegen Trittbrettfahrer tun?

2017-10-26 Thread Jörg Schmidt
Hallo Günter, *, 

> From: Günter Feierabend [mailto:feierab...@telia.com] 

> Tatsächlich weiß ich nicht, inwieweit das Führen des Namens 
> „OpenOffice" im Titel der Internetseite erlaubt ist, wenn 
> diese von Trittbrettfahrern eingerichtet wurde, die nichts 
> mit der offiziellen Seite (egal ob Apache oder damals .org) 
> und der mit ihr verbundenen Arbeit zu tun haben.

nur mal 'fürs Protokoll':

ob es im aktuellen Fall überhaupt um die von mir beispielhaft genannte Seite, 
oder irgendeine Seite mit "openoffice" als Namensbestandteil geht weiß ich 
schlichtweg nicht weil der Betroffene es nicht geschrieben hat. Vielleicht 
meldet er sich (auf der internationalen dev) ja nochmal und sagt dazu etwas 
Genaueres.

> Dies wird 
> wohl auch mit (nicht-)eingetragenen Marken- oder Produktnamen 
> zusammenhängen?

Ich denke jenseits der Markeneinträge (die es aber gibt) ist die 'Politik' von 
Apache dazu etwas inkonsequent.



Gruß
Jörg


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



Re: Check for Updates Manually Can't find OpenOffice Version 4.1.4

2017-10-26 Thread Marcus

Am 26.10.2017 um 17:18 schrieb Dave Fisher:

In order to not overload the infrastructure we wait a week or so to update the 
check for updates version.


this user mail seems to be a good indicator to activate the update 
service in the next days.


Marcus




On Oct 25, 2017, at 11:23 PM, BOBBY ZIINO  wrote:

It's been a week since OpenOffice 4.1.4 has been released and it still isn't 
found via the Check for Updates setting mechanism when searched for manually, 
is it still yet to be uploaded to the Apache OpenOffice servers or is it no 
longer provided through the Check For Updates mechanism.


I previously updated to 4.1.3 from 4.1.2 from the Check for Updates checker 
mechanism.



-
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

2017-10-26 Thread Marcus

Am 26.10.2017 um 07:03 schrieb Peter kovacs:

Am 25. Oktober 2017 21:25:42 MESZ schrieb Marcus :


Sure, it's not yet written in stop. But when we need to build it it has to be.

Furthermore, when releasing from "test" or "release" or similar, what
to
do with these branches? I hope you do not suggest "then we can recycle
them and reuse for the next build". ;-)

Why do you think it is a problem to go by state?


I cannot see what is behind the names. "test" - from what? Is it still 
for 4.1.x or the new 4.2.0 or what? I really think it is not clear for 
everyone.


And again:
Never, never, ever reuse a branch that has seen a release. You will 
destroy the history. In the worst case you will loose the overview and 
therefore loose time when you actually don't have it.


Creating a new branch just after we have released a version is fast and 
cheap.


Marcus




Am 25. Oktober 2017 19:44:39 MESZ schrieb Marcus

:

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.


+1
This is an good and cheap idea to speed things up.

Marcus



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



Was können wir gegen Trittbrettfahrer tun?

2017-10-26 Thread Jörg Schmidt
Hallo zusammen,

gerade kam auf der internationalen dev-Liste eine verärgerte Email eines 
Anwenders der offensichtlich von dritter Seite reingelegt (nicht originaler 
Download mit Werbung/Spam) und um eine Spende betrogen wurde.

Ich habe dem Anwender dort auf der Liste geantwortet, aber das macht natürlich 
nicht seine Verärgerung und seinen finanziellen Schaden wett.

Leider weiß ich auch nicht was man im Kern der Sachen tun kann, denn Seiten wie 
z.B.:
https://www.openoffice.de sind imho juristisch wasserfest - aber welcher 
Anwender erkennt denn das es sich dabei nicht um die originale OpenOffice-Seite 
handelt? 
Dehalb sind Anwender natürlich moralisch zurecht verärgert und für uns als 
Projekt dürften solche Dinge extrem schädlich sein weil sie natürlich 
weitererzählt werden.


Mein Vorschlag wäre auf die internationale dev-Liste zu posten, um zu 
besprechen das es möglicherweise sinnvoll sein ist  wenn Apache dazu eine 
Pressemeldung herausgibt um die Öffentlichkeit zu informieren und in der 
Hoffnung das zumindest einige Zeitschriften das als kurze Notiz weitergeben.


Was meint ihr?



Gruß
Jörg


P.S.
Bitte kein Missverständnis, die Rechtslage ist eindeutig d.h. jeder darf AOO 
zum Download anbieten und jeder darf für sich dafür um Spenden werben, trotzdem 
fühlen sich dadurch Nutzer betrogen.
Andererseits bin ich kein Jurist und vielleicht würde ein Gericht in manchen 
Einzelfällen doch anders werten (also im Interesse des Anwenders), aber es ist 
unrealisatisch das deswegen Anwender Klage erheben.

Bitte auch kein Missverständnis zu meiner persönlichen Meinung, denn natürlich 
befürworte ich im Generellen die lizensrechtskonforme Weitergabe von AOO durch 
Dritte, ggf. auch gegen Geld und ich bin sicher das das in der Mehrzahl der 
Fälle ich korrekter Weise erfolgt, also für den Anwender ersuchtlich ist bei 
wem er für was bezahlt oder spendet.
In den Fällen wo der Nutzer jedoch getäuscht wird liegt der Fall völlig anders.

 


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



Re: Meine Daten

2017-10-26 Thread Jörg Schmidt
Hallo Herr Leßweng, 

> nach dem installieren Ihres Openoffice Downlads wurde 
> angegeben, dass ich 
> meine Email Adresse bestätigen soll,
> daraufhin wurde eine Seite vom Computerwissen geöffnet, 
> außerdem erhalte 
> ich unerwünschte Angebote. 

Das kann nur sein wenn Sie OpenOffice von anderen Seiten heruntergeladen haben 
und nicht von der Originalseite.
Zuverlässig erhalten Sie OPenOffice nur über die originale Download-Seite:
deutsch:
http://www.openoffice.org/de/download/index.html

international:
http://www.openoffice.org/download/index.html

Haben Sie den Download nach dem Herunterladen verifiziert, indem Sie die 
MD5-Prüfsumme überprüft haben, wie z.B. im deutschsprachigen 
Installationshandbuch beschrieben?

siehe:
in deutsch:
http://www.prooo-box.org/live/dokumentation/office/installations_handbuch.pdf

oder Anleitung in englisch:
https://www.openoffice.org/download/checksums.html

> Das finde ich nicht richtig, wie 
> Sie mit meinen 
> Daten, die ich Vertrauensvoll Ihnen gegeben habe, umgehen.

wir haben keine Daten von Ihnen.

> Letzte Woche habe ich noch Ihnen gespendet,

Wie denn konkret und an wen? Spenden explizit an das OpenOffice-Projekt sind 
ohne Weiteres garnicht möglich, sondern nur direkt an die Apache Software 
Foundation (http://apache.org/).
Haben Sie wirklich an Letztere gespendet?

> Bitte 
> geben Sie meine Daten nicht weiter und Informieren Sie die 
> Firmen, denen 
> Sie meine Daten gegeben haben, dass ich dies nicht wünsche.

Das können wir nicht, denn wir haben keine Daten von Ihnen. Ohne weitere 
Informationen kann ich momentan auch nur mutmaßen das Sie auf irgendeinen 
Trittbrettfahrer hereingefallen sind der Sie hinters Licht geführt hat.
Beispielsweise ist die Seite https://www.openoffice.de/ keine zu unserem 
Projekt gehörige Seite, sondern eine rein privat betriebene Seite, auf die wir 
natürlich keinerlei Einfluss haben.



Gruß
Jörg


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



Re: Meine Daten

2017-10-26 Thread FR web forum
>after installing your Openoffice Downlad it was stated that I should 
>confirm my email address,
Sorry but no e-mail address is required if OpenOffice is downloaded from 
official site:
http://www.openoffice.org/de/download/
This page above is specific for german language.

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



Meine Daten

2017-10-26 Thread lessweng-wer...@t-online.de
Sehr geehrte Damen und Herren,
nach dem installieren Ihres Openoffice Downlads wurde angegeben, dass ich 
meine Email Adresse bestätigen soll,
daraufhin wurde eine Seite vom Computerwissen geöffnet, außerdem erhalte 
ich unerwünschte Angebote. Das finde ich nicht richtig, wie Sie mit meinen 
Daten, die ich Vertrauensvoll Ihnen gegeben habe, umgehen.
Letzte Woche habe ich noch Ihnen gespendet, nun bin ich Enttäuscht. Bitte 
geben Sie meine Daten nicht weiter und Informieren Sie die Firmen, denen 
Sie meine Daten gegeben haben, dass ich dies nicht wünsche.
Mit freundlichen Grüßen: Werner Leßweng
 
Dear Sir or Madam,
 

after installing your Openoffice Downlad it was stated that I should 
confirm my email address,
 

then a page of computer knowledge was opened and I received unwanted 
offers. I can not find the right way to deal with my data, which I have 
trusted you.
 

Last week I donated to you, now I am disappointed. Please do not give my 
data further and inform the companies to which you have given my data that 
I do not wish this.
 

Yours sincerely: Werner Leßweng


 
Gesendet mit Telekom Mail  - kostenlos 
und sicher für alle!

[Build] Redland, Raptor on Trunk needs attention

2017-10-26 Thread Dave Fisher
Hi -

Truckman has made updates to Redland and components on trunk that are not in 
the current release branches. See the commit messages for his reasoning.

The Redland, Rasqal and Raptor configuration has complicated scripting and 
configuration. The configure files have some of the worst indentation I’ve seen 
and have so many options. Something is failing with the $PKG_CONFIG and I am 
concerned that this is difficult to debug and even then how would I know if I 
got the options correct.

I see that Jim did commit one fix for Raptor. It looks like the trunk build 
needs some care.

I am switching my test build over to the 4.1.4 branch.

Regards,
Dave



signature.asc
Description: Message signed with OpenPGP


Re: Check for Updates Manually Can't find OpenOffice Version 4.1.4

2017-10-26 Thread Dave Fisher
Hi -

In order to not overload the infrastructure we wait a week or so to update the 
check for updates version.

We are all volunteers here. Thanks for the prompt.

Regards,
Dave

Sent from my iPhone

> On Oct 25, 2017, at 11:23 PM, BOBBY ZIINO  wrote:
> 
> Hi there,
> 
> 
> It's been a week since OpenOffice 4.1.4 has been released and it still isn't 
> found via the Check for Updates setting mechanism when searched for manually, 
> is it still yet to be uploaded to the Apache OpenOffice servers or is it no 
> longer provided through the Check For Updates mechanism.
> 
> 
> I previously updated to 4.1.3 from 4.1.2 from the Check for Updates checker 
> mechanism.
> 
> 
> Regards Bobby


-
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

2017-10-26 Thread Jim Jagielski
Yeah, I kinda figured out what your hypothesis was... I'll need
to think about this some more.
> On Oct 26, 2017, at 8:34 AM, Patricia Shanahan  wrote:
> 
> OK, forget that hypothesis. You have even done the next test I would have 
> asked for if the line 288 breakpoint was not reached.
> 
> I'll need to think up a new hypothesis. I'm planning to go groom a couple of 
> horses this morning, but I'll work on this in the afternoon.
> 
> On 10/26/2017 5:01 AM, Jim Jagielski wrote:
>> I set breakpoints on both:
>>(lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx --line 288
>>(lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate
>> Breakpoint 4: where = 
>> libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), address = 
>> 0x00010070a260
>> and when opening up the corrupted file, neither breakpoint
>> was reached. :/
>> -
>> 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

2017-10-26 Thread Patricia Shanahan
OK, forget that hypothesis. You have even done the next test I would 
have asked for if the line 288 breakpoint was not reached.


I'll need to think up a new hypothesis. I'm planning to go groom a 
couple of horses this morning, but I'll work on this in the afternoon.


On 10/26/2017 5:01 AM, Jim Jagielski wrote:

I set breakpoints on both:

(lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx --line 288
(lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate
Breakpoint 4: where = 
libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), address = 
0x00010070a260

and when opening up the corrupted file, neither breakpoint
was reached. :/
-
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

2017-10-26 Thread Jim Jagielski
I set breakpoints on both:

   (lldb) breakpoint set --file main/sfx2/source/appl/linkmgr2.cxx --line 288
   (lldb) breakpoint set -n LinkManager::GetUserAllowsLinkUpdate
Breakpoint 4: where = 
libsfx.dylib`sfx2::LinkManager::GetUserAllowsLinkUpdate(Window*), address = 
0x00010070a260

and when opening up the corrupted file, neither breakpoint
was reached. :/
-
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

2017-10-26 Thread Jim Jagielski
+1. Having a branch ready to roll is cheap insurance.


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



Access denied on Dictionaries page

2017-10-26 Thread Marco A.G.Pinto
Hello!

I had committed V2017.11.01 of the English dictionaries.

I noticed that the release notes had the AU+CA+US there when they were
updated in the previous release.

So, I fixed the text and uploaded a new .OXT.

Now I get an access error in the official page:
http://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice

Could someone take a look at it?

Thanks!

Kind regards,
    >Marco A.G.Pinto
  --

-- 


signature.asc
Description: OpenPGP digital signature


Re: [PROPOSAL] Managing branches for future releases

2017-10-26 Thread Don Lewis
On 26 Oct, Peter kovacs wrote:
> 
> 
> Am 25. Oktober 2017 21:25:42 MESZ schrieb Marcus :
>>Am 25.10.2017 um 20:50 schrieb Peter kovacs:
>>> Why do you want to branch all the time with names that can change? I
>>think it is an expensive way of getting flexibility. I suggest a more
>>abstract branches.
>>> 
>>> Why not have 4 permanent branches that are dev/trunc , test, hotfix
>>and Release?
>>> 
>>> Dev/trunc would contain latest development.
>>> Test would contain the latest release candidate that gets prepared.
>>It bases of from dev and propagates to release.
>>> Hotfix is the one that bases on release and propagates back to
>>release branch.
>>> With this schema you have an abstract way in doing the same thing
>>without the limitation of naming.
>>
>>sorry but this is totally confusing.
>>
>>> We could even post vote result into comments. When propagate version
>>to release. Also we can decide on release name at the latest possible
>>moment.
>>
>>Deciding on the name (or better said version numnber) when the build
>>is
>>
>>nearly finished dooesn't make sense. We need to know what we are
>>working on.
>>
>>> It would be less confusing especially if we rename a release. (4.2.0
>>is not final decided. But we may now have branch. Or we wait until we
>>have decided but that would delay the result until we are done with
>>the naming.)
>>
>>There are only a few moments when we need to agree on a new version 
>>number. The new release will be one of these. Currently it's 4.2.0 but 
>>who knows.
> That's exactly what I mean. Our release cycles are slow. We have
> decided a year ago we stick to 4.2.0 but it was not final it seems. 
> Better decide on the name when ready.
>>
>>Every bugfix release is a minor release. So, only the last number will 
>>be increased.
> I think this is not critical. But decision 4.2.0 or 5.0.0 is more
> political then technical.
> 
>>
>>Sure, it's not yet written in stop. But when we need to build it it
>>has to be.
>>
>>Furthermore, when releasing from "test" or "release" or similar, what
>>to 
>>do with these branches? I hope you do not suggest "then we can recycle 
>>them and reuse for the next build". ;-)
> Why do you think it is a problem to go by state?
> 
> I see the benefit that there is no need to delete 4.1.5 if we do not
> need it. We simply promote the code in the branch from release. Maybe
> state as a comment. Rebase to 4.2.0 release. Done.
> Also a new release is done the same way.
> No need for new branches and maybe explain people what's the release
> because release manager had no time to make a new branch.

We need at least as many branches as we have releases.  If you try to
reuse a branch, then you will lose whatever history is associated with
it.  We have branches for 4.1.0, 4.1.1, 4.1.2, 4.1.3, 4.1.4, plus lots
more for older releases.  That allows us to look at what is in each of
those releases as well as look back at the changes that were part of
those releases.  Running the svn command to create a new branch isn't
the time consuming part.  Most of the effort is spent on tweaking all
of the source files that contain version-specific information,
solenv/inc/minor.mk for one example.  That would still have to be done
manually even if you try to reuse a branch.

svn doesn't have anything like git rebase.  Even in git, rebase is
problematic.  If you rebase a branch checked out from a remote
repository, git won't let you push it back.  If you do a force push,
you'll hose anyone else who has a copy of that branch.  They'll have to
delete their local copy of that branch and refetch.  About the only way
to safely use rebase is to create a new local branch, rebase that, and
then push to create a new remote branch.

> Also I think for people. Testers will check out test or hot fix (Maybe
> maintenance is a better word). A someone who wants a release version
> simply checks out release branch. There is no need explaining anyone
> which one is the current release what is maintenance.

You really can't reuse hotfix branches, you have to generate unique
names for them.  With a git-based workflow, you might want to create a
new branch to test a hotfix, and you can delete it after the fix has
been tested successfully and merged, but later creating a new branch
with the same name will cause problems.  Anybody who has a copy of the
old version of that branch will run into problems when trying to pull
the new version because the history of the local and remote copies will
not match.

> It is error proove.
> Also if you think on auto builds. No maintenance. If you use version
> names you have to make sure that the release builder always points at
> release branch. That maintenance builder points on the current machine
> branch. There will be always manually tasks involved. And manuall
> means potential failures.
> 
> Also if you think on our release cycles we have discussed.
> 1-2 years for feature release
> 1-2 additional maintenance. Maybe we do more