Re: 4.1.4_release_blocker requested: [Issue 125147] CRASH applying styles to text

2016-10-06 Thread Marcus

Am 10/06/2016 11:55 PM, schrieb Matthias Seidel:

Yes, there were at least 5 (overlapping) issues solved by these 2 fixes.

Should they all be requested as release blocker?


when all are similar but have the same root cause, then it doesn't make 
sense.


Let's see:
When this one got fixed in the (coming soon) AOO414 branch in SVN, all 
related issues can be tested. If all are no longer occurring, then goal 
reached. Otherwise we have to look at the remaining issues separately.


Marcus




Am 06.10.2016 um 23:19 schrieb Marcus:

+1
I remember, too, that there were more than 1 report.

Marcus



Am 10/06/2016 10:13 PM, schrieb bugzi...@apache.org:

Matthias Seidel   has askedfor
4.1.4_release_blocker:
Issue 125147: CRASH applying styles to text
https://bz.apache.org/ooo/show_bug.cgi?id=125147


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



Re: {Dicuss] [Vote]

2016-10-06 Thread Marcus

Am 10/06/2016 11:45 PM, schrieb Peter Kovacs:


I can only make some time for testing on the 8th Okt.  Is that okay if I
take my vote on this last moment?


of course, that's the advantage of the time frame. Take your time.

Marcus




Keith N. McKenna  schrieb am Do., 6. Okt. 2016,
19:48:


Ariel Constenla-Haile wrote:

On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:

Ariel;

In all the builds that I have been involved in with AOO we have

included

a link to a Bugzilla query for all bugs fixed by that release.My

concern

was 2 fold. One that it would give a wrong impression to anyone that
followed the link and the second was to try to keep Bugzilla up to

date.


If it is possible we should construct a query that excludes anything in
Product = Build Tools for the Release Notes.


I think calling out the important stuff directly in the release notes

but

providing a Bugzilla link that shows everything, including tools, is a
reasonable compromise. However, I am very open to suggestions for

improving

the release notes.


IMO yes, there should be a link to the bugzilla query, but it does not
make sense to mention those build-related bugs individually.


Regards


I agree there is no need to highlight those types of bugs individually.
I will remove the individual mention of them from the 4.1.3 Release Notes.

Keith


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



Re: Post vote release actions

2016-10-06 Thread Patricia Shanahan



On 10/6/2016 5:42 AM, Marcus wrote:

Am 10/05/2016 06:27 PM, schrieb Andrea Pescetti:

Patricia Shanahan wrote:

RM: Update
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3 to show
vote result etc.


The only important thing to update is that the release is available,
since the page stays archived.


RM: Edit
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes


release notes to delete "DRAFT" note. - RM


Someone will also have to call for translations and coordinate
translations.


RM: Use svn to move
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ to
https://dist.apache.org/repos/dist/release/openoffice/4.1.3/. See
https://lists.apache.org/thread.html/0b3416c973088efdf60056d2aae7f6cee0bd125be4370f3c0ff5324b@%3Cdev.openoffice.apache.org%3E


for Ariel's tip on how to do this without a full checkout.


SVN moves by URL. So you never need a full checkout for the mv (Ariel
was addressing another issue, i.e., how to add a file to a directory
without a full checkout). For moving, this command will work from any
directory (one line):

$ svn mv https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1
https://dist.apache.org/repos/dist/release/openoffice/4.1.3


Someone with SourceForge access: Upload to SourceForge using rsync.


This does need a full checkout (a full export to be precise). I have
access, as several other PMC members; I can take care of this.


Modify OpenOffice web pages to reflect the new release.
Press release and announcement on apache.org home page.


I'll take care about the website updates ...


...and for the post on https://blogs.apache.org/OOo/ I have access, but
I thinks others do too, so I'd leave this to someone else - even though
it may be a simple copy/paste from the announcement.


... and could also do a blog post if nobody else want to do this.


Thanks. Would you like to be the point person working with Sally on the 
press release? It would be smooth to coordinate themes between press 
release and blog post.


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



Re: {Dicuss] [Vote]

2016-10-06 Thread Keith N. McKenna
Peter Kovacs wrote:
> Hi,
> 
> I can only make some time for testing on the 8th Okt.  Is that okay if I
> take my vote on this last moment?
> 
As long as it is before 22:00 UTC it should be fine. That is the
earliest that the vote can end.

> Keith N. McKenna  schrieb am Do., 6. Okt. 2016,
> 19:48:
> 
>> Ariel Constenla-Haile wrote:
>>> On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:
> Ariel;
>
> In all the builds that I have been involved in with AOO we have
>> included
> a link to a Bugzilla query for all bugs fixed by that release.My
>> concern
> was 2 fold. One that it would give a wrong impression to anyone that
> followed the link and the second was to try to keep Bugzilla up to
>> date.
>
> If it is possible we should construct a query that excludes anything in
> Product = Build Tools for the Release Notes.

 I think calling out the important stuff directly in the release notes
>> but
 providing a Bugzilla link that shows everything, including tools, is a
 reasonable compromise. However, I am very open to suggestions for
>> improving
 the release notes.
>>>
>>> IMO yes, there should be a link to the bugzilla query, but it does not
>>> make sense to mention those build-related bugs individually.
>>>
>>>
>>> Regards
>>>
>> I agree there is no need to highlight those types of bugs individually.
>> I will remove the individual mention of them from the 4.1.3 Release Notes.
>>
>> Keith
>>
>> --
> 
> Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
> wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
> werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
> Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
> kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
> Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
> konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
> wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
> verhandeln.
> 




signature.asc
Description: OpenPGP digital signature


Re: {Dicuss] [Vote]

2016-10-06 Thread Patricia Shanahan

No problem. I won't close the vote early.

On 10/6/2016 2:45 PM, Peter Kovacs wrote:

Hi,

I can only make some time for testing on the 8th Okt.  Is that okay if I
take my vote on this last moment?

Keith N. McKenna  schrieb am Do., 6. Okt. 2016,
19:48:


Ariel Constenla-Haile wrote:

On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:

Ariel;

In all the builds that I have been involved in with AOO we have

included

a link to a Bugzilla query for all bugs fixed by that release.My

concern

was 2 fold. One that it would give a wrong impression to anyone that
followed the link and the second was to try to keep Bugzilla up to

date.


If it is possible we should construct a query that excludes anything in
Product = Build Tools for the Release Notes.


I think calling out the important stuff directly in the release notes

but

providing a Bugzilla link that shows everything, including tools, is a
reasonable compromise. However, I am very open to suggestions for

improving

the release notes.


IMO yes, there should be a link to the bugzilla query, but it does not
make sense to mention those build-related bugs individually.


Regards


I agree there is no need to highlight those types of bugs individually.
I will remove the individual mention of them from the 4.1.3 Release Notes.

Keith

--


Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
verhandeln.



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



Re: [VOTE] Release Apache OpenOffice 4.1.3 RC1

2016-10-06 Thread Pedro

+1

Installed successfully version 4.1.3 RC1 pt on Windows XP Pro x86 SP3 
pt, Win7 Pro x64 Sp1 pt and Win 10 Home x64 pt


Added successfully en_US Language pack on the 3 systems.

Opened several documents of types ods, xls(x), odt, doc(x) without any 
problems.


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



Re: 4.1.4_release_blocker requested: [Issue 125762] Writer crashed when I tried to close bibliography table

2016-10-06 Thread Marcus

+1
At least from source code it looks like an easy and not a risky fix.

Marcus



Am 10/06/2016 10:15 PM, schrieb bugzi...@apache.org:

Matthias Seidel  has askedfor
4.1.4_release_blocker:
Issue 125762: Writer crashed when I tried to close bibliography table
https://bz.apache.org/ooo/show_bug.cgi?id=125762


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



Re: Post vote release actions

2016-10-06 Thread Andrea Pescetti

Ariel Constenla-Haile wrote:

IIRC the last step is updating the update feed so that current
installations get an update notification.
This is under subversion at
https://svn.apache.org/repos/asf/openoffice/updates-site/trunk/


This traditionally happens a few days (up to one week) after release, to 
avoid unwanted peaks of traffic. This is something I can take care of - 
provided someone takes care of extracting a list with tasks a names from 
this thread!


Regards,
  Andrea.

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



Re: [VOTE] Release Apache OpenOffice 4.1.3 RC1

2016-10-06 Thread Jim Jagielski
+1 (binding)
  source testing:
o Checked signature and hashes
o Checked source formats contain identical files.
o Built and tested en-US on OSX 10.11

  binary testing:
o Tested en-US app on OSX 10.11, 10.10

> On Oct 5, 2016, at 5:07 PM, Patricia Shanahan  wrote:
> 
> The Apache OpenOffice 4.1.3 source and binaries, 
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain several 
> bug fixes. See the draft release notes at 
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes
> 
> Please vote on releasing it as 4.1.3 by replying to this thread
> 
> [ ] +1 Approve, with description of any testing you have done
> [ ] 0 Abstain
> [ ] -1 Disapprove, with explanation.
> 
> In addition, if you are a PMC member please indicate "Binding" if you intend 
> to cast a binding vote, which requires a build and test from source.
> 
> Please tag any discussion, rather than votes, with [DISCUSS][VOTE].
> 
> The vote will conclude no sooner than 10 p.m UTC on Saturday, October 8th, 
> 2016.
> 
> -
> 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: Release 4.1.4 - Blocker candidates

2016-10-06 Thread Matthias Seidel
Yes! ;-)

Thanks a lot...

Matthias


Am 06.10.2016 um 21:34 schrieb Marcus:
> Am 10/06/2016 08:25 PM, schrieb Matthias Seidel:
>> Sorry, I still can't set flags.
>> Logged out and in again...
>
> OK, I've now looked into the documentation and it says the user need
> the "editbugs" permissions which I've now set for your account.
>
> I hope it is now working.
>
> Marcus
>
>
>
>> Am 05.10.2016 um 13:17 schrieb Marcus:
>>> Am 10/05/2016 01:08 PM, schrieb Matthias Seidel:
 Am 05.10.2016 um 12:59 schrieb Marcus:
> Am 10/05/2016 12:24 PM, schrieb Matthias Seidel:
>> Sorry for highjacking this thread...
>
> please don't. Just create a mail with new subject or at least change
> the subject as I've done now.

 OK, I will do so in the future.

>
>> I would like to promote some issues as release blocker for 4.1.4.
>> The
>> issues are fixed in trunk and the code changes are minimal.
>>
>> What would be the best way, as I see no possibility in my
>> bugzilla-account?
>
> In the BZ issue look for "Flags". Click on "set flags" and choose the
> "4.1.4_release_blocker" with its question mark. Then in any case
> write
> a comment (why it should go into 4.1.4, if known range and risk of
> the
> fix and others). This will send a mail to dev@, so that the Release
> Manager can decide.

 Well, I see no "Flags" in my account. Even not in the issue that I
 reported myself...
 So I am not supposed to set a flag...
>>>
>>> OK, I've changed permissions for your account. Please check again.
>>>
>>> Marcus
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature


4.1.4_release_blocker requested: [Issue 125762] Writer crashed when I tried to close bibliography table

2016-10-06 Thread bugzilla
Matthias Seidel  has asked  for
4.1.4_release_blocker:
Issue 125762: Writer crashed when I tried to close bibliography table
https://bz.apache.org/ooo/show_bug.cgi?id=125762
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



4.1.4_release_blocker requested: [Issue 125147] CRASH applying styles to text

2016-10-06 Thread bugzilla
Matthias Seidel  has asked  for
4.1.4_release_blocker:
Issue 125147: CRASH applying styles to text
https://bz.apache.org/ooo/show_bug.cgi?id=125147
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Release 4.1.4 - Blocker candidates

2016-10-06 Thread Marcus

Am 10/06/2016 08:25 PM, schrieb Matthias Seidel:

Sorry, I still can't set flags.
Logged out and in again...


OK, I've now looked into the documentation and it says the user need the 
"editbugs" permissions which I've now set for your account.


I hope it is now working.

Marcus




Am 05.10.2016 um 13:17 schrieb Marcus:

Am 10/05/2016 01:08 PM, schrieb Matthias Seidel:

Am 05.10.2016 um 12:59 schrieb Marcus:

Am 10/05/2016 12:24 PM, schrieb Matthias Seidel:

Sorry for highjacking this thread...


please don't. Just create a mail with new subject or at least change
the subject as I've done now.


OK, I will do so in the future.




I would like to promote some issues as release blocker for 4.1.4. The
issues are fixed in trunk and the code changes are minimal.

What would be the best way, as I see no possibility in my
bugzilla-account?


In the BZ issue look for "Flags". Click on "set flags" and choose the
"4.1.4_release_blocker" with its question mark. Then in any case write
a comment (why it should go into 4.1.4, if known range and risk of the
fix and others). This will send a mail to dev@, so that the Release
Manager can decide.


Well, I see no "Flags" in my account. Even not in the issue that I
reported myself...
So I am not supposed to set a flag...


OK, I've changed permissions for your account. Please check again.

Marcus


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



Re: [VOTE] Release Apache OpenOffice 4.1.3 RC1

2016-10-06 Thread Keith N. McKenna
Patricia Shanahan wrote:
> The Apache OpenOffice 4.1.3 source and binaries,
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain
> several bug fixes. See the draft release notes at
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes
> 
> 
> Please vote on releasing it as 4.1.3 by replying to this thread
> 
> [ ] +1 Approve, with description of any testing you have done
> [ ] 0 Abstain
> [ ] -1 Disapprove, with explanation.
> 
> In addition, if you are a PMC member please indicate "Binding" if you
> intend to cast a binding vote, which requires a build and test from source.
> 
> Please tag any discussion, rather than votes, with [DISCUSS][VOTE].
> 
> The vote will conclude no sooner than 10 p.m UTC on Saturday, October
> 8th, 2016.
[ X ] +1 Approve Non-Binding Confirmed the PGP signature,Confirmed md5
and sha356 hashes, Installed with no problems.
[ ] 0 Abstain
[ ] -1 Disapprove, with explanation.




signature.asc
Description: OpenPGP digital signature


Re: Release 4.1.4 - Blocker candidates

2016-10-06 Thread Matthias Seidel
Sorry, I still can't set flags.
Logged out and in again...

Matthias


Am 05.10.2016 um 13:17 schrieb Marcus:
> Am 10/05/2016 01:08 PM, schrieb Matthias Seidel:
>> Am 05.10.2016 um 12:59 schrieb Marcus:
>>> Am 10/05/2016 12:24 PM, schrieb Matthias Seidel:
 Sorry for highjacking this thread...
>>>
>>> please don't. Just create a mail with new subject or at least change
>>> the subject as I've done now.
>>
>> OK, I will do so in the future.
>>
>>>
 I would like to promote some issues as release blocker for 4.1.4. The
 issues are fixed in trunk and the code changes are minimal.

 What would be the best way, as I see no possibility in my
 bugzilla-account?
>>>
>>> In the BZ issue look for "Flags". Click on "set flags" and choose the
>>> "4.1.4_release_blocker" with its question mark. Then in any case write
>>> a comment (why it should go into 4.1.4, if known range and risk of the
>>> fix and others). This will send a mail to dev@, so that the Release
>>> Manager can decide.
>>
>> Well, I see no "Flags" in my account. Even not in the issue that I
>> reported myself...
>> So I am not supposed to set a flag...
>
> OK, I've changed permissions for your account. Please check again.
>
> Marcus
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature


Re: {Dicuss] [Vote]

2016-10-06 Thread Keith N. McKenna
Ariel Constenla-Haile wrote:
> On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:
>>> Ariel;
>>>
>>> In all the builds that I have been involved in with AOO we have included
>>> a link to a Bugzilla query for all bugs fixed by that release.My concern
>>> was 2 fold. One that it would give a wrong impression to anyone that
>>> followed the link and the second was to try to keep Bugzilla up to date.
>>>
>>> If it is possible we should construct a query that excludes anything in
>>> Product = Build Tools for the Release Notes.
>>
>> I think calling out the important stuff directly in the release notes but
>> providing a Bugzilla link that shows everything, including tools, is a
>> reasonable compromise. However, I am very open to suggestions for improving
>> the release notes.
> 
> IMO yes, there should be a link to the bugzilla query, but it does not
> make sense to mention those build-related bugs individually.
> 
> 
> Regards
> 
I agree there is no need to highlight those types of bugs individually.
I will remove the individual mention of them from the 4.1.3 Release Notes.

Keith



signature.asc
Description: OpenPGP digital signature


RE: {Dicuss] [Vote] Summary

2016-10-06 Thread Dennis E. Hamilton
+1

Great analysis and working things out: pats, arielch, marcus.

> -Original Message-
> From: Patricia Shanahan [mailto:p...@acm.org]
> Sent: Thursday, October 6, 2016 06:00
> To: dev@openoffice.apache.org
> Subject: Re: {Dicuss] [Vote] Summary
> 
> This thread has morphed a bit, and I think a summary may be useful at
> this time.
> 
> It started with Keith pointing out, correctly, that I was taking a short
> cut by starting the vote before all the relevant bugs had been marked
> "Fixed", although after I was sure they were all fixed in reality. That
> aspect was quickly resolved by Ariel updating the bugs in question. All
> 4.1.3 release blocker bugs are now marked as fixed.
> 
> It then shifted into a discussion of what should be in the release
> notes. There are three classes of Bugzilla issues involved:
> 
> 1. Fixes affecting the behavior of binaries. Listing these in the
> release notes is non-controversial.
> 
> 2. Administrative changes, changing the release number in various
> places.
> 
> 3. Fixes to the build systems. Because of the year time lapse since
> 4.1.2, there was an accumulation of issues that affect building in
> various environments.
> 
> The question was how to handle the second and third classes. They are
> uninteresting, and in some cases incomprehensible, to the vast majority
> of AOO users. The plan is to only mention "interesting" bugs directly in
> the release notes, but include the URL for a Bugzilla query that shows
> all the fixes.
> 
> 
> -
> 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: {Dicuss] [Vote] Summary

2016-10-06 Thread Patricia Shanahan
This thread has morphed a bit, and I think a summary may be useful at 
this time.


It started with Keith pointing out, correctly, that I was taking a short 
cut by starting the vote before all the relevant bugs had been marked 
"Fixed", although after I was sure they were all fixed in reality. That 
aspect was quickly resolved by Ariel updating the bugs in question. All 
4.1.3 release blocker bugs are now marked as fixed.


It then shifted into a discussion of what should be in the release 
notes. There are three classes of Bugzilla issues involved:


1. Fixes affecting the behavior of binaries. Listing these in the 
release notes is non-controversial.


2. Administrative changes, changing the release number in various places.

3. Fixes to the build systems. Because of the year time lapse since 
4.1.2, there was an accumulation of issues that affect building in 
various environments.


The question was how to handle the second and third classes. They are 
uninteresting, and in some cases incomprehensible, to the vast majority 
of AOO users. The plan is to only mention "interesting" bugs directly in 
the release notes, but include the URL for a Bugzilla query that shows 
all the fixes.



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



Re: Post vote release actions

2016-10-06 Thread Ariel Constenla-Haile
On Wed, Oct 05, 2016 at 08:26:17AM -0700, Patricia Shanahan wrote:
> I plan to start the 4.1.3 vote today. This is a draft of the action list
> assuming the vote passes. Please help by correcting, expanding, and adding
> anything missing.
> 
> RM: Update https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3 to
> show vote result etc.
> 
> RM: Edit
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes
> release notes to delete "DRAFT" note. - RM
> 
> RM: Use svn to move
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ to
> https://dist.apache.org/repos/dist/release/openoffice/4.1.3/. See 
> https://lists.apache.org/thread.html/0b3416c973088efdf60056d2aae7f6cee0bd125be4370f3c0ff5324b@%3Cdev.openoffice.apache.org%3E
> for Ariel's tip on how to do this without a full checkout.
> 
> Someone with SourceForge access: Upload to SourceForge using rsync.
> 
> Modify OpenOffice web pages to reflect the new release.
> 
> Press release and announcement on apache.org home page.

IIRC the last step is updating the update feed so that current
installations get an update notification.

This is under subversion at
https://svn.apache.org/repos/asf/openoffice/updates-site/trunk/

Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


signature.asc
Description: Digital signature


Re: [VOTE] Release Apache OpenOffice 4.1.3 RC1

2016-10-06 Thread Marcus

+1 Binding

What I've done:

SVN:
- Build the AOO413 branch with release options.
- Checked the RAT scan report that no license problems were shown.

Source package:
- Build the software with release options.
- Checked the provided hash values.

Binary packages:
- Checked the provided packages:
  - Linux 64-bit: full installs + langpacks for en-US + de
  - Windows 10: full installs + langpacks for en-US + de

Marcus



Am 10/05/2016 11:07 PM, schrieb Patricia Shanahan:

The Apache OpenOffice 4.1.3 source and binaries,
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain
several bug fixes. See the draft release notes at
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes


Please vote on releasing it as 4.1.3 by replying to this thread

[ ] +1 Approve, with description of any testing you have done
[ ] 0 Abstain
[ ] -1 Disapprove, with explanation.

In addition, if you are a PMC member please indicate "Binding" if you
intend to cast a binding vote, which requires a build and test from source.

Please tag any discussion, rather than votes, with [DISCUSS][VOTE].

The vote will conclude no sooner than 10 p.m UTC on Saturday, October
8th, 2016.


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



Re: New AOO414 branch?

2016-10-06 Thread Marcus

Am 10/05/2016 11:37 PM, schrieb Andrea Pescetti:

Can we open the AOO414 branch? Everything seems to show that 4.1.3 will
be coming in a week or so and for sure there is no further code work to
do on it. So I'd like to have an AOO414 branch where (once they are
approved) we can start merging changes. OpenOffice 4.1.4 is not going to
take another year, so better start early.


I don't see any problems to do it now.

But IMHO the developers should decide this. In the worst case they have 
to merge more code than normally. ;-)


Marcus


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



Re: Post vote release actions

2016-10-06 Thread Marcus

Am 10/05/2016 06:27 PM, schrieb Andrea Pescetti:

Patricia Shanahan wrote:

RM: Update
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3 to show
vote result etc.


The only important thing to update is that the release is available,
since the page stays archived.


RM: Edit
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes

release notes to delete "DRAFT" note. - RM


Someone will also have to call for translations and coordinate
translations.


RM: Use svn to move
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/ to
https://dist.apache.org/repos/dist/release/openoffice/4.1.3/. See
https://lists.apache.org/thread.html/0b3416c973088efdf60056d2aae7f6cee0bd125be4370f3c0ff5324b@%3Cdev.openoffice.apache.org%3E

for Ariel's tip on how to do this without a full checkout.


SVN moves by URL. So you never need a full checkout for the mv (Ariel
was addressing another issue, i.e., how to add a file to a directory
without a full checkout). For moving, this command will work from any
directory (one line):

$ svn mv https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1
https://dist.apache.org/repos/dist/release/openoffice/4.1.3


Someone with SourceForge access: Upload to SourceForge using rsync.


This does need a full checkout (a full export to be precise). I have
access, as several other PMC members; I can take care of this.


Modify OpenOffice web pages to reflect the new release.
Press release and announcement on apache.org home page.


I'll take care about the website updates ...


...and for the post on https://blogs.apache.org/OOo/ I have access, but
I thinks others do too, so I'd leave this to someone else - even though
it may be a simple copy/paste from the announcement.


... and could also do a blog post if nobody else want to do this.

Marcus


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



[DISSCUSS] [VOTE] Release Apache OpenOffice 4.1.3 RC1

2016-10-06 Thread Marcus

Am 10/06/2016 12:51 PM, schrieb Jörg Schmidt:

From: Patricia Shanahan [mailto:p...@acm.org]
Sent: Wednesday, October 05, 2016 11:07 PM
To: dev@openoffice.apache.org
Subject: [VOTE] Release Apache OpenOffice 4.1.3 RC1

The Apache OpenOffice 4.1.3 source and binaries,
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain
several bug fixes. See the draft release notes at
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3
+Release+Notes

Please vote on releasing it as 4.1.3 by replying to this thread

[ ] +1 Approve, with description of any testing you have done
[ ] 0 Abstain
[ ] -1 Disapprove, with explanation.


[x] 0 Abstain


(Sorry for this decision but the thread "{Dicuss] [Vote]" is not completely 
clear for me)


then I don't understand why you don't wait until it is clear and then 
cast your vote. Voting is open until Oct, 08th. Or take part in the 
discussion of the BZ thread. ;-)


Please think again about changing your vote until the end of the period.

Marcus


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



Re: {Dicuss] [Vote]

2016-10-06 Thread Marcus

Am 10/06/2016 02:33 PM, schrieb Patricia Shanahan:

On 10/6/2016 5:21 AM, Marcus wrote:

Am 10/06/2016 01:52 PM, schrieb Marcus:

...

I'll take a look into the issue list, update the release notes with
interesting issues for the average user and keep the full details to the
link of BZ issues.


done.

I've also added a line for the BZ issue 126622 "Base 4.1.2 does not open
Tables and Queries in Mac OSX" that it is no longer occurring.


I hate marking things fixed when they mysteriously disappear, because
anything that mysteriously disappears can reappear, probably at the
least convenient possible time.

I think, based on Ariel's comment #28 on
https://bz.apache.org/ooo/show_bug.cgi?id=126622, that we no longer have
a mysterious disappearance, but an actual fix:

It is fixed by switching from building on Mac OS X El Capitan with Xcode
7 to building on 4.1.3 on macOS Sierra with Xcode 8.

I am going to be offline for several hours starting in about an hour.
Can you update the release notes to show this?


and done :-)

Marcus


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



Re: Testing 4.1.3 - release notes

2016-10-06 Thread Patricia Shanahan



On 10/6/2016 5:29 AM, Marcus wrote:

Am 10/05/2016 12:23 AM, schrieb Patricia Shanahan:

Could people working on the bugzilla entries check the status and update
as appropriate?


I've seen now all issues as "Resolved - Fixed" - or "Verified - Fixed".


Note that I did not include the Mac Tables and Queries issue,
https://bz.apache.org/ooo/show_bug.cgi?id=126622, in the release notes
because I did not see enough confirmation that it is fixed. I have now


IMHO this has changed in the meantime. I've added this also to the
release notes.


denied it 4.1.3 release blocker, but added a request for 4.1.4.


I hope you don't mind that I've deleted the 4.1.4 blocker request.


No problem. I only filed the request to make sure it did not get lost.
Fixed by choice of build environment is much better.

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



Re: {Dicuss] [Vote]

2016-10-06 Thread Patricia Shanahan

On 10/6/2016 5:21 AM, Marcus wrote:

Am 10/06/2016 01:52 PM, schrieb Marcus:

...

I'll take a look into the issue list, update the release notes with
interesting issues for the average user and keep the full details to the
link of BZ issues.


done.

I've also added a line for the BZ issue 126622 "Base 4.1.2 does not open
Tables and Queries in Mac OSX" that it is no longer occurring.


I hate marking things fixed when they mysteriously disappear, because 
anything that mysteriously disappears can reappear, probably at the 
least convenient possible time.


I think, based on Ariel's comment #28 on 
https://bz.apache.org/ooo/show_bug.cgi?id=126622, that we no longer have 
a mysterious disappearance,  but an actual fix:


It is fixed by switching from building on Mac OS X El Capitan with Xcode 
7 to building on 4.1.3 on macOS Sierra with Xcode 8.


I am going to be offline for several hours starting in about an hour. 
Can you update the release notes to show this?


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



Re: Testing 4.1.3 - release notes

2016-10-06 Thread Marcus

Am 10/05/2016 12:23 AM, schrieb Patricia Shanahan:

Could people working on the bugzilla entries check the status and update
as appropriate?


I've seen now all issues as "Resolved - Fixed" - or "Verified - Fixed".


Note that I did not include the Mac Tables and Queries issue,
https://bz.apache.org/ooo/show_bug.cgi?id=126622, in the release notes
because I did not see enough confirmation that it is fixed. I have now


IMHO this has changed in the meantime. I've added this also to the 
release notes.



denied it 4.1.3 release blocker, but added a request for 4.1.4.


I hope you don't mind that I've deleted the 4.1.4 blocker request.

Marcus




On 10/4/2016 2:47 PM, Marcus wrote:

Am 10/04/2016 10:31 PM, schrieb Patricia Shanahan:

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes




ah, thanks. I've updated some text (e.g., separated the sec issue into
an own paragraph) and updated the link for the BZ issue list as it still
points to 4.0.1.

I'm a bit worried about the many issues that are not fixed, resolved,
closed [1].

But besides this it's OK. So, we are also done here.

[1]
https://bz.apache.org/ooo/buglist.cgi?f1=flagtypes.name=equals=Importance_format=advanced=4.1.3_release_blocker%2B



Marcus




On 10/4/2016 1:29 PM, Marcus wrote:

OK, binary and source code testing is on a good way.

What about the release notes. Are these somewhere reachable/readable
already?


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



4.1.4_release_blocker denied: [Issue 126622] Base 4.1.2 does not open Tables and Queries in Mac OSX

2016-10-06 Thread bugzilla
Marcus  has denied Patricia Shanahan 's
request for 4.1.4_release_blocker:
Issue 126622: Base 4.1.2 does not open Tables and Queries in Mac OSX
https://bz.apache.org/ooo/show_bug.cgi?id=126622

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



Re: {Dicuss] [Vote]

2016-10-06 Thread Marcus

Am 10/06/2016 01:52 PM, schrieb Marcus:

Am 10/06/2016 05:10 AM, schrieb Patricia Shanahan:


On 10/5/2016 5:51 PM, Keith N. McKenna wrote:

Ariel Constenla-Haile wrote:

On Wed, Oct 05, 2016 at 07:17:27PM -0400, Keith N. McKenna wrote:

Patricia Shanahan wrote:

I believe, based on my tracking and testing, that the release
blockers
are all fixed. I was hoping the people working on the bugs,
especially
those who requested release_blocker, will update them ASAP.


I have no doubt that they have been fixed, but they need to be updated
as we link to a query for them from the Release Notes and what message
does it give to the world if the Release Notes show Release
Blockers as
still open?


Most of these bugs don't make any sense in the release notes, they are
too aoo-build specific.


Regards


Ariel;

In all the builds that I have been involved in with AOO we have included
a link to a Bugzilla query for all bugs fixed by that release.My concern
was 2 fold. One that it would give a wrong impression to anyone that
followed the link and the second was to try to keep Bugzilla up to date.

If it is possible we should construct a query that excludes anything in
Product = Build Tools for the Release Notes.


I think calling out the important stuff directly in the release notes
but providing a Bugzilla link that shows everything, including tools, is
a reasonable compromise. However, I am very open to suggestions for
improving the release notes.


that was also my idea. I don't like to hide things as we do open source.
Fixing problems when building is part of that. And it is not a secret
that we would have more fixes in the build area than in previous releases.

I'll take a look into the issue list, update the release notes with
interesting issues for the average user and keep the full details to the
link of BZ issues.


done.

I've also added a line for the BZ issue 126622 "Base 4.1.2 does not open 
Tables and Queries in Mac OSX" that it is no longer occurring.


Marcus


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



Re: {Dicuss] [Vote]

2016-10-06 Thread Marcus

Am 10/06/2016 05:10 AM, schrieb Patricia Shanahan:


On 10/5/2016 5:51 PM, Keith N. McKenna wrote:

Ariel Constenla-Haile wrote:

On Wed, Oct 05, 2016 at 07:17:27PM -0400, Keith N. McKenna wrote:

Patricia Shanahan wrote:

I believe, based on my tracking and testing, that the release blockers
are all fixed. I was hoping the people working on the bugs, especially
those who requested release_blocker, will update them ASAP.


I have no doubt that they have been fixed, but they need to be updated
as we link to a query for them from the Release Notes and what message
does it give to the world if the Release Notes show Release Blockers as
still open?


Most of these bugs don't make any sense in the release notes, they are
too aoo-build specific.


Regards


Ariel;

In all the builds that I have been involved in with AOO we have included
a link to a Bugzilla query for all bugs fixed by that release.My concern
was 2 fold. One that it would give a wrong impression to anyone that
followed the link and the second was to try to keep Bugzilla up to date.

If it is possible we should construct a query that excludes anything in
Product = Build Tools for the Release Notes.


I think calling out the important stuff directly in the release notes
but providing a Bugzilla link that shows everything, including tools, is
a reasonable compromise. However, I am very open to suggestions for
improving the release notes.


that was also my idea. I don't like to hide things as we do open source. 
Fixing problems when building is part of that. And it is not a secret 
that we would have more fixes in the build area than in previous releases.


I'll take a look into the issue list, update the release notes with 
interesting issues for the average user and keep the full details to the 
link of BZ issues.


Marcus


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



Re: [Issue 126622] Base 4.1.2 does not open Tables and Queries in Mac OSX

2016-10-06 Thread Marcus

Am 10/06/2016 01:43 PM, schrieb Marcus:

As I can see every reporter told us that the issue is no longer
occurring with 4.1.3-rc1. Therefore I would like to set this issue to
"Verified - Without code" - course with an additional comment - as the
real fix is not known so far.


Ariel had the same idea in the same minute - must be magic. ;-)

Marcus




Am 10/06/2016 10:19 AM, schrieb bugzi...@apache.org:

https://bz.apache.org/ooo/show_bug.cgi?id=126622

--- Comment #27 from tintin60 ---
Hi,

I'm at the origin of the issue 126623
(https://bz.apache.org/ooo/show_bug.cgi?id=126623)

I just tested AOO 4.1.3 as suggested and I confirm no more problem
with Data
Bases tables. It works.


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



Re: [Issue 126622] Base 4.1.2 does not open Tables and Queries in Mac OSX

2016-10-06 Thread Marcus
As I can see every reporter told us that the issue is no longer 
occurring with 4.1.3-rc1. Therefore I would like to set this issue to 
"Verified - Without code" - course with an additional comment - as the 
real fix is not known so far.


Marcus



Am 10/06/2016 10:19 AM, schrieb bugzi...@apache.org:

https://bz.apache.org/ooo/show_bug.cgi?id=126622

--- Comment #27 from tintin60  ---
Hi,

I'm at the origin of the issue 126623
(https://bz.apache.org/ooo/show_bug.cgi?id=126623)

I just tested AOO 4.1.3 as suggested and I confirm no more problem with Data
Bases tables. It works.


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



Re: [VOTE] Release Apache OpenOffice 4.1.3 RC1

2016-10-06 Thread Carl Marcum

+1 Binding

Source testing: Checked signature and hashes. Checked that the three 
source formats contain identical files. Built and tested en-US on Fedora 
20 x86-64.
Ran automated BVT tests and compared against current 4.1.2 install. (1 
additional test passed than 4.1.2)


Binary testing: Tested en-US binary on Fedora 20 x86-64.
Ran automated BVT tests and compared against my source build 4.1.3 RC1 
with identical results.


Thanks,
Carl

On 10/05/2016 05:07 PM, Patricia Shanahan wrote:
The Apache OpenOffice 4.1.3 source and binaries, 
https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain 
several bug fixes. See the draft release notes at 
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Release+Notes


Please vote on releasing it as 4.1.3 by replying to this thread

[ ] +1 Approve, with description of any testing you have done
[ ] 0 Abstain
[ ] -1 Disapprove, with explanation.

In addition, if you are a PMC member please indicate "Binding" if you 
intend to cast a binding vote, which requires a build and test from 
source.


Please tag any discussion, rather than votes, with [DISCUSS][VOTE].

The vote will conclude no sooner than 10 p.m UTC on Saturday, October 
8th, 2016.


-
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: [VOTE] Release Apache OpenOffice 4.1.3 RC1

2016-10-06 Thread Jörg Schmidt
> From: Patricia Shanahan [mailto:p...@acm.org] 
> Sent: Wednesday, October 05, 2016 11:07 PM
> To: dev@openoffice.apache.org
> Subject: [VOTE] Release Apache OpenOffice 4.1.3 RC1
> 
> The Apache OpenOffice 4.1.3 source and binaries, 
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.3-rc1/, contain 
> several bug fixes. See the draft release notes at 
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3
> +Release+Notes
> 
> Please vote on releasing it as 4.1.3 by replying to this thread
> 
> [ ] +1 Approve, with description of any testing you have done
> [ ] 0 Abstain
> [ ] -1 Disapprove, with explanation.

[x] 0 Abstain


(Sorry for this decision but the thread "{Dicuss] [Vote]" is not completely 
clear for me)


Jörg


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