RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

> -Original Message-
> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
> Sent: Monday, August 15, 2016 21:05
> To: q...@openoffice.apache.org; dev@openoffice.apache.org
> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> 
> 
> Dennis E. Hamilton wrote:
> > BETA 0.2.0 IS NOW AVAILABLE
> >
> > This is a cleanup version.  It is hoped that this will be the last
> change before bumping the version to 1.0.0 and making general
> availability.
> >
> > One important change:
> >
> > The names of the files have been changed.
> >
> > The README is now named README-4.1.2-patch1-Windows.txt.
> >
> > The zip and the related .asc, .md5, .sha1, and .sha256 files all
> have the base name
> > apache-openoffice-4.1.2-patch1-Win_x86.zip
> >
> > The two scripts also have simpler names:
> >
> > APPLY-4.1.2-patch1.bat
> > REVERT-4.1.2-patch1.bat
> >
> > The files are still available at
> >
> >  patch1/Windows>
> [knmc]
> the link should read
> <
[orcmid] 
https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/binaries/Windows/>
[orcmid] 

Right you are.  Thanks for the quick check.
> 
> Regards
> Keith
> >
> > Now it is worth testing enough to know there is no regression and that
> APPLY and REVERT operate properly as before.
> >
> >  - Dennis
> >
[ ... ]



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

tried to register for open office formus

[Colby Menning]

Do not know how to sign electronically.  Had example sites but I don't know
how to fill this signature line in to complete my registration and ask:
How do I get off "Variale" in Viewing and reset to "100%"?
Also the margins are set to default which I cannot ovveride and set to "0"
in "Numbering and bullets".

Can not download open office - times out

[Loni Brock]

Problem descriptionExchange this text to describe the problem 


(What does not work? What do you expect?)

Browser variables

Values

navigator.appCodeNameMozilla
navigator.appNameNetscape
navigator.appVersion5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 
(KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36
navigator.platformWin32
navigator.oscpuundefined
navigator.cpuClassundefined
navigator.productGecko
navigator.productSub20030107
navigator.vendorGoogle Inc.
navigator.vendorSub
navigator.languageen-US
navigator.browserLanguageundefined
navigator.userLanguageundefined
navigator.systemLanguageundefined
navigator.userAgentMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 
(KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36
Debian / Ubuntu / IceWeasel ?No / No / No

Stable Release




JavaScript functions/variables

Values

Language ISO codeen-US
Language ISO code (from select box)en-US
Release matrix platform position (full)11
Release matrix platform position (lp)12
Release matrix platform array datay,134
Release matrix language array dataen-US,English (US),English 
(US),y,download/index.html
UI platform nameWindows (EXE)
UI platform name (not supported)
Platform (short)win32
URL platform name (full)Win_x86_install
URL platform name (lp)Win_x86_langpack
URL platform name (from select box)win32
Version (from select box)4.1.2
File name (full)Apache_OpenOffice_4.1.2_Win_x86_install_en-US.exe
File name (lp)Apache_OpenOffice_4.1.2_Win_x86_langpack_en-US.exe
File extension.exe
File size (full) (MByte)134
File size (lp) (MByte)18
Release infoMilestone AOO412m3 | Build ID 9782 | SVN r1709699 | Released 
2015-10-28
Download file link 
(full)http://sourceforge.net/projects/openofficeorg.mirror/files/4.1.2/binaries/en-US/Apache_OpenOffice_4.1.2_Win_x86_install_en-US.exe/download
Download file link 
(lp)http://sourceforge.net/projects/openofficeorg.mirror/files/4.1.2/binaries/en-US/Apache_OpenOffice_4.1.2_Win_x86_langpack_en-US.exe/download
Checksum file link (full) (here for 
MD5)http://archive.apache.org/dist/openoffice/4.1.2/binaries/en-US/Apache_OpenOffice_4.1.2_Win_x86_install_en-US.exe.md5
Checksum file link (lp) (here for 
MD5)http://archive.apache.org/dist/openoffice/4.1.2/binaries/en-US/Apache_OpenOffice_4.1.2_Win_x86_langpack_en-US.exe.md5
Base URL to 
Sourceforge.nethttp://sourceforge.net/projects/openofficeorg.mirror/files/4.1.2/binaries/
Base URL to Apache Archivehttp://archive.apache.org/dist/openoffice/4.1.2
getLinkSelection() (download URL)undefined
isLanguageSupported() (true/false) ?true
Show the sub-box (true/false) ?true
General error (true/false) ?false

Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Keith N. McKenna]

Dennis E. Hamilton wrote:
> BETA 0.2.0 IS NOW AVAILABLE
>
> This is a cleanup version.  It is hoped that this will be the last change 
> before bumping the version to 1.0.0 and making general availability.
>
> One important change:
>
> The names of the files have been changed.  
>
> The README is now named README-4.1.2-patch1-Windows.txt.
>
> The zip and the related .asc, .md5, .sha1, and .sha256 files all have the 
> base name
> apache-openoffice-4.1.2-patch1-Win_x86.zip
>
> The two scripts also have simpler names:
>
> APPLY-4.1.2-patch1.bat
> REVERT-4.1.2-patch1.bat
>
> The files are still available at
>
> 
[knmc]
the link should read


Regards
Keith
>
> Now it is worth testing enough to know there is no regression and that APPLY 
> and REVERT operate properly as before.
>
>  - Dennis
>
>> -Original Message-
>> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
>> Sent: Thursday, August 11, 2016 21:08
>> To: dev@openoffice.apache.org
>> Cc: q...@openoffice.apache.org
>> Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
>>
>> BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE
>>
>> The scripts make life much easier, since users don't have to go hunting
>> for anything and digging around in operating-system locations.
>>
>> You should be able to go through the procedure that uses the automated
>> steps pretty easily.
>>
>> It is very important to know the difficulties that arise or whether
>> there were none.
>>
>> The material is available at
>> > patch1/binaries/Windows>.
>>
>>  - Dennis
>>
>>
>>
>>> -Original Message-
>>> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
>>> Sent: Wednesday, August 10, 2016 18:01
>>> To: dev@openoffice.apache.org
>>> Cc: q...@openoffice.apache.org
>>> Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
>>>
>>> Beta version 0.1.0 is now nearing completion.
>>>
>>> It will include two scripts, one for applying the patch, the other for
>>> reverting the patch.
>>>
>>> The .zip will also have a copy of the original 4.1.2 tl.dll as well as
>>> the new one.  These are used in the procedures to verify the files
>> that
>>> are present in the OpenOffice configuration in order to apply the
>> patch
>>> and also to remove it.
>>>
>>> Next steps:
>>>  * Additional path testing of the two scripts and verification that
>>> operation on Windows XP and on Windows 10 work as expected.
>> [orcmid]
>>
>> Done
>>
>> It is also much easier to work through the patch checks using the
>> scripts.
>>>  * Updating of the README to reflect the availability of the batch-
>> file
>>> scripts as well as the manual procedure if ever needed.
>> [orcmid]
>>
>> Done
>>
>>>  * Although the Zips already carry executable code (i.e., DLLs) there
>>> may be some Antivirus push-back where the policy is to not allow .zip
>>> files with scripts in them.  The README will also have to address that
>>> possibility.
>> [orcmid]
>>
>> I forgot that at the last minute.  I will put that into the next
>> version.  Meanwhile, those who check these procedures should report any
>> AV objections they ran into.
>>
>>
>>>  - Dennis
>>>
 -Original Message-
 From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
 Sent: Monday, August 8, 2016 09:58
 To: dev@openoffice.apache.org
 Cc: q...@openoffice.apache.org
 Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

 Alpha version 0.0.1 of README-4.1.2-patch1-apply-Windows.txt has
>> been
 introduced into the files (and the .zip) at
 .

 This version reflects suggestions by Marcus Lange, Pedro Lino, and
>>> Keith
 McKenna.  Suggestions that are not (yet) implemented will be
>> discussed
 in replies to their messages and on the bugzilla issue at
 .


 By its nature, this material is intended for users operating on
>>> Windows.
 In some cases, incompatible forms are used on the Subversion server
 where the above files are situated.  Version 0.0.1 attempts to
 accommodate for this incompatibility.  In continuing to verify the
 procedure, please indicate whether there are (now) difficulties
>> using
 the text files, especially on Windows.

 Users of Linux systems may have difficulties with some utilities for
 which the Windows versions of the same tool (e.g., md5sum) do not
 produce Linux-acceptable line endings.  It is useful to know if that
>>> is
 still the case.  The files have been confirmed to be usable using
>> the
 utilities built for use on Windows.

 For future versions, the use of HTML ins

Re: upgrading bundled openssl

[Don Lewis]

On 15 Aug, Pedro Giffuni wrote:
> Hi Don;
> 
> Thanks for working on this!
> 
> Two crazy ideas here:
> 
> 1) Perhaps bundling libressl instead of openssl make sense?

I thought about that, but it seemed like a bigger step.  Also I don't
think curl is compatible.  When I tried building a set of FreeBSD
packages with libressl, I didn't get to OpenOffice because curl didn't
build.

> 2) It would be really nice if we were able to use encryption in other 
> components: apr-utils and curl, for example.

I'll look into that.

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

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

BETA 0.2.0 IS NOW AVAILABLE

This is a cleanup version.  It is hoped that this will be the last change 
before bumping the version to 1.0.0 and making general availability.

One important change:

The names of the files have been changed.  

The README is now named README-4.1.2-patch1-Windows.txt.

The zip and the related .asc, .md5, .sha1, and .sha256 files all have the 
base name
apache-openoffice-4.1.2-patch1-Win_x86.zip

The two scripts also have simpler names:

APPLY-4.1.2-patch1.bat
REVERT-4.1.2-patch1.bat

The files are still available at



Now it is worth testing enough to know there is no regression and that APPLY 
and REVERT operate properly as before.

 - Dennis

> -Original Message-
> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> Sent: Thursday, August 11, 2016 21:08
> To: dev@openoffice.apache.org
> Cc: q...@openoffice.apache.org
> Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> BETA 0.1.0 WITH AUTOMATED SCRIPTS IS NOW AVAILABLE
> 
> The scripts make life much easier, since users don't have to go hunting
> for anything and digging around in operating-system locations.
> 
> You should be able to go through the procedure that uses the automated
> steps pretty easily.
> 
> It is very important to know the difficulties that arise or whether
> there were none.
> 
> The material is available at
>  patch1/binaries/Windows>.
> 
>  - Dennis
> 
> 
> 
> > -Original Message-
> > From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> > Sent: Wednesday, August 10, 2016 18:01
> > To: dev@openoffice.apache.org
> > Cc: q...@openoffice.apache.org
> > Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> >
> > Beta version 0.1.0 is now nearing completion.
> >
> > It will include two scripts, one for applying the patch, the other for
> > reverting the patch.
> >
> > The .zip will also have a copy of the original 4.1.2 tl.dll as well as
> > the new one.  These are used in the procedures to verify the files
> that
> > are present in the OpenOffice configuration in order to apply the
> patch
> > and also to remove it.
> >
> > Next steps:
> >  * Additional path testing of the two scripts and verification that
> > operation on Windows XP and on Windows 10 work as expected.
> [orcmid]
> 
> Done
> 
> It is also much easier to work through the patch checks using the
> scripts.
> >
> >  * Updating of the README to reflect the availability of the batch-
> file
> > scripts as well as the manual procedure if ever needed.
> [orcmid]
> 
> Done
> 
> >
> >  * Although the Zips already carry executable code (i.e., DLLs) there
> > may be some Antivirus push-back where the policy is to not allow .zip
> > files with scripts in them.  The README will also have to address that
> > possibility.
> [orcmid]
> 
> I forgot that at the last minute.  I will put that into the next
> version.  Meanwhile, those who check these procedures should report any
> AV objections they ran into.
> 
> 
> >
> >  - Dennis
> >
> > > -Original Message-
> > > From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> > > Sent: Monday, August 8, 2016 09:58
> > > To: dev@openoffice.apache.org
> > > Cc: q...@openoffice.apache.org
> > > Subject: RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> > >
> > > Alpha version 0.0.1 of README-4.1.2-patch1-apply-Windows.txt has
> been
> > > introduced into the files (and the .zip) at
> > >  > > patch1/binaries/Windows>.
> > >
> > > This version reflects suggestions by Marcus Lange, Pedro Lino, and
> > Keith
> > > McKenna.  Suggestions that are not (yet) implemented will be
> discussed
> > > in replies to their messages and on the bugzilla issue at
> > > .
> > >
> > >
> > > By its nature, this material is intended for users operating on
> > Windows.
> > > In some cases, incompatible forms are used on the Subversion server
> > > where the above files are situated.  Version 0.0.1 attempts to
> > > accommodate for this incompatibility.  In continuing to verify the
> > > procedure, please indicate whether there are (now) difficulties
> using
> > > the text files, especially on Windows.
> > >
> > > Users of Linux systems may have difficulties with some utilities for
> > > which the Windows versions of the same tool (e.g., md5sum) do not
> > > produce Linux-acceptable line endings.  It is useful to know if that
> > is
> > > still the case.  The files have been confirmed to be usable using
> the
> > > utilities built for use on Windows.
> > >
> > > For future versions, the use of HTML instead of text will be
> > considered.
> > > HTML does not have white-space incompatibility problems across
> > different
> > > platforms. The HTML will also be digitally-signed as a means of

Re: upgrading bundled openssl

[Pedro Giffuni]

Hi Don;

Thanks for working on this!

Two crazy ideas here:

1) Perhaps bundling libressl instead of openssl make sense?

2) It would be really nice if we were able to use encryption in other 
components: apr-utils and curl, for example.


Pedro.

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

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

> -Original Message-
> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
> Sent: Saturday, August 13, 2016 21:24
> To: q...@openoffice.apache.org
> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> Dennis;
> Attached is an odt file with mark-ups and comments for a couple of
> changes for the readme. For the general public release I have been
> working on a draft of a more formal format that can be used as a
> template for future situations such as this.
> 
> Keith
[orcmid] 

Thanks Keith.  The markup was simple enough to reflect in the 0.2.0 BETA that 
is going up shortly.

 - Dennis
> 
> Dennis E. Hamilton wrote:
> >
> >> -Original Message-
> >> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
> >> Sent: Friday, August 12, 2016 13:49
> >> To: q...@openoffice.apache.org; dev@openoffice.apache.org
> >> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> >>
> >> Attached is a text file with the tests that I ran and the results of
> >> each. The only problem encountered was in verifying tl.dll.new with
> the
> >> .asc signature file. This was due to the web of trust issue discussed
> >> earlier in this thread.Patricia's signature had not been certified by
> >> anyone. One I elevated the Owner Trust level and certified it the
> >> verification passed.
> >>
> >> I will finish reviewing the latest documentation and send any
> comments
> >> or suggested changes under separate cover.
> >>
> >> Regards
> >> Keith
[ ... ]



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

RE: [PATCH DOWNLOAD] Draft for the hotfix webpage

[Dennis E. Hamilton]

> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Monday, August 15, 2016 13:43
> To: dev@openoffice.apache.org
> Subject: Re: [PATCH DOWNLOAD] Draft for the hotfix webpage
> 
> Am 08/15/2016 09:10 PM, schrieb Dennis E. Hamilton:
> >
> >> -Original Message-
> >> From: Kay sch...@apache.org [mailto:ksch...@apache.org]
> >> Sent: Monday, August 15, 2016 08:59
> >> To: dev@openoffice.apache.org
> >> Subject: Re: [PATCH DOWNLOAD] Draft for the hotfix webpage
> >>
> >> On 08/13/2016 02:16 PM, Marcus wrote:
> >>> As we have now the patched library file and Readme for all
> platforms,
> >>> IMHO not much more is needed to go public with the hotfix. Therefore
> >>> I've created a draft version of the hotfix download webpage:
> >>>
> >>> http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> >> patch1/hotfix.html
> >>>
> >>> Please review and tell me your feedback.
> > [orcmid]
> >
> > I have a number of items.  I can fix the URLs in (2) below after I
> have updated the Windows set.
> >
> >1. This is worded as if it is the advisory.  I assume this is,
> rather, something that should be linked to from an update of the
> advisory.  I request that it be a description of the HotFix.  It could
> link to the advisory, of course.  RECOMMENDATION: Have the emphasis be
> on this describing release of the hotfix for CVE-2016-1513.
> 
> OK, seems indeed not clear enough.
> 
> >2. Download and Installation.  Currently, this page is at
> >  patch1/hotfix.html>.  It has *ABSOLUTE* URLs to the binaries and source
> and the various hashes.  WHEN GENERAL DISTRIBUTION OCCURS, this page and
> all of the binaries and source pages will be at
> > .
> 
> Please remember that it's just a draft of what is available at the
> moment. ;-) That's why the URLs for source and binaries differ already.
> Of course all URLs will change when everything is available at dist/ and
> no longer dev/.
> 
> RECOMMENDATION: In the Download&  Installation table, make all URLS
> *RELATIVE* to the HotFix page, since when it is staged to release and
> then to archive, the links will always work.
> >   NOTE. When we make general distribution, we stage the HotFix
> HTML page and the binaries subfolder to
> > 
> using SVN copies.  In 24-48 hours or so that material will show up
> automatically on archive.apache.org and we can make the general
> distribution announcement.  The dist.apache.org materials can be removed
> when that happens.  WARNING. The Windows material is not ready, and some
> renaming will happen.  That should all be done by the end of Tuesday
> (GMT).
> 
> The current location of the hotfix webpage is of course is not the final
> one. It will be there where the other webpages are: at w.oo.o.
> 
> I've just put it into SVN to have it not yet on the public OO website.
[orcmid] 

LOL.  I thought that is where you wanted to keep it [;<).  Because it is so 
specific to this HotFix, I think it would be great to leave it with the 
downloads and the archive.apache.org site, but link to it from openoffice.org. 
 
> 
> >3. Next Step under Download and Installation.  The README for
> Windows addresses the way to Unzip and provides important information
> about how the extract is into a folder of a default-determined name.  I
> don't know if the others provide comparable information and/or operating
> from a terminal is assumed.
> 
> Yes, more (Linux) or less (Mac) it should be comparable.
> 
> >4. How to verify the download&  installation.  Verifying the Zip is
> sufficient.  The table does not identify the files those check cases are
> from so it is not at all clear what value this is.  RECOMMENDATION: If
> it is valuable, we should include the additional hashes inside the Zips,
> and provide the size and time stamp information in the individual README
> files.
> 
> Yes, right. "Old file" and "New file" is for sure not exact enough which
> file it is about. And the other file-based data can be moved to the
> Readme's, too.
> 
>  > That way there is no redundancy and the information is maintained in
>  > exactly one place.
> 
> 
> Ahm, no. ;-) At the moment we have it at a single place. When we split
> it into the 4 Readme's then we have 4 places to maintain.
> 
> 
> But at the end you are right. The webpage contains some details that
> should be moved to the respective Readme.
> 
> I'll finish the changes when I'm back from a trip on Thursday or Friday.
> 
> Thanks for your feedback.
> 
> Marcus
> 
> 
> 
> >> Looks good to me.
> >>
> >> --
> >> Kay Schenk
> >> Apache OpenOffice
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [Discuss] New template on cwiki for Release Notes

[Keith N. McKenna]

Andrea Pescetti wrote:
> On 03/08/2016 Keith N. McKenna wrote:
>> Using the template facilities of the cwiki I have created a template for
>> creating Release Notes for AOO. It utilizes variables to fill in
>> repetitive entries, and instructive text to aid in writing.
> 
> Tested. It's very helpful, thank you. Automatic variables help a lot in
> avoiding errors related to copy/paste.
> 
> Regards,
>   Andrea.
Thanks for the feedback Andrea. If there are other templates that would
be helpful I will be more than happy to take a crack at creating them.




signature.asc
Description: OpenPGP digital signature

Re: [PATCH DOWNLOAD] Draft for the hotfix webpage

[Marcus]

Am 08/15/2016 09:10 PM, schrieb Dennis E. Hamilton:



-Original Message-
From: Kay sch...@apache.org [mailto:ksch...@apache.org]
Sent: Monday, August 15, 2016 08:59
To: dev@openoffice.apache.org
Subject: Re: [PATCH DOWNLOAD] Draft for the hotfix webpage

On 08/13/2016 02:16 PM, Marcus wrote:

As we have now the patched library file and Readme for all platforms,
IMHO not much more is needed to go public with the hotfix. Therefore
I've created a draft version of the hotfix download webpage:

http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-

patch1/hotfix.html


Please review and tell me your feedback.

[orcmid]

I have a number of items.  I can fix the URLs in (2) below after I have updated 
the Windows set.

   1. This is worded as if it is the advisory.  I assume this is, rather, 
something that should be linked to from an update of the advisory.  I request 
that it be a description of the HotFix.  It could link to the advisory, of 
course.  RECOMMENDATION: Have the emphasis be on this describing release of the 
hotfix for CVE-2016-1513.


OK, seems indeed not clear enough.


   2. Download and Installation.  Currently, this page is at
.  
It has *ABSOLUTE* URLs to the binaries and source and the various hashes.  WHEN 
GENERAL DISTRIBUTION OCCURS, this page and all of the binaries and source pages will 
be at
.


Please remember that it's just a draft of what is available at the 
moment. ;-) That's why the URLs for source and binaries differ already. 
Of course all URLs will change when everything is available at dist/ and 
no longer dev/.


RECOMMENDATION: In the Download&  Installation table, make all URLS 
*RELATIVE* to the HotFix page, since when it is staged to release and 
then to archive, the links will always work.

  NOTE. When we make general distribution, we stage the HotFix HTML page 
and the binaries subfolder to
  using SVN 
copies.  In 24-48 hours or so that material will show up automatically on 
archive.apache.org and we can make the general distribution announcement.  The 
dist.apache.org materials can be removed when that happens.  WARNING. The Windows 
material is not ready, and some renaming will happen.  That should all be done by the 
end of Tuesday (GMT).


The current location of the hotfix webpage is of course is not the final 
one. It will be there where the other webpages are: at w.oo.o.


I've just put it into SVN to have it not yet on the public OO website.


   3. Next Step under Download and Installation.  The README for Windows 
addresses the way to Unzip and provides important information about how the 
extract is into a folder of a default-determined name.  I don't know if the 
others provide comparable information and/or operating from a terminal is 
assumed.


Yes, more (Linux) or less (Mac) it should be comparable.


   4. How to verify the download&  installation.  Verifying the Zip is 
sufficient.  The table does not identify the files those check cases are from so it 
is not at all clear what value this is.  RECOMMENDATION: If it is valuable, we 
should include the additional hashes inside the Zips, and provide the size and time 
stamp information in the individual README files.


Yes, right. "Old file" and "New file" is for sure not exact enough which 
file it is about. And the other file-based data can be moved to the 
Readme's, too.


> That way there is no redundancy and the information is maintained in
> exactly one place.


Ahm, no. ;-) At the moment we have it at a single place. When we split 
it into the 4 Readme's then we have 4 places to maintain.



But at the end you are right. The webpage contains some details that 
should be moved to the respective Readme.


I'll finish the changes when I'm back from a trip on Thursday or Friday.

Thanks for your feedback.

Marcus




Looks good to me.

--
Kay Schenk
Apache OpenOffice


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

Re: upgrading bundled openssl

[Marcus]

Am 08/15/2016 10:16 PM, schrieb Don Lewis:

I started working on upgrading the bundled version of openssl to 1.0.2h.
So far I've discovered that building in on Windows requires nasm.  That
will need to be documented in the build requirements / procedures.  I
think I need to add a check to configure to look for it and bail out if
nasm isn't installed, but I haven't gotten that far yet.  The Windows
buildbot will need to have nasm installed.


puh, so many dependencis and it's still increasing. ;-)

Thanks for working this out.

Marcus


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

upgrading bundled openssl

[Don Lewis]

I started working on upgrading the bundled version of openssl to 1.0.2h.
So far I've discovered that building in on Windows requires nasm.  That
will need to be documented in the build requirements / procedures.  I
think I need to add a check to configure to look for it and bail out if
nasm isn't installed, but I haven't gotten that far yet.  The Windows
buildbot will need to have nasm installed.

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

RE: [PATCH DOWNLOAD] Draft for the hotfix webpage

[Dennis E. Hamilton]

> -Original Message-
> From: Kay sch...@apache.org [mailto:ksch...@apache.org]
> Sent: Monday, August 15, 2016 08:59
> To: dev@openoffice.apache.org
> Subject: Re: [PATCH DOWNLOAD] Draft for the hotfix webpage
> 
> 
> 
> On 08/13/2016 02:16 PM, Marcus wrote:
> > As we have now the patched library file and Readme for all platforms,
> > IMHO not much more is needed to go public with the hotfix. Therefore
> > I've created a draft version of the hotfix download webpage:
> >
> > http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/hotfix.html
> >
> > Please review and tell me your feedback.
[orcmid] 

I have a number of items.  I can fix the URLs in (2) below after I have updated 
the Windows set.

  1. This is worded as if it is the advisory.  I assume this is, rather, 
something that should be linked to from an update of the advisory.  I request 
that it be a description of the HotFix.  It could link to the advisory, of 
course.  RECOMMENDATION: Have the emphasis be on this describing release of the 
hotfix for CVE-2016-1513.

  2. Download and Installation.  Currently, this page is at 
.  
It has *ABSOLUTE* URLs to the binaries and source and the various hashes.  WHEN 
GENERAL DISTRIBUTION OCCURS, this page and all of the binaries and source pages 
will be at 
.  RECOMMENDATION: In 
the Download & Installation table, make all URLS *RELATIVE* to the HotFix page, 
since when it is staged to release and then to archive, the links will always 
work.  
 NOTE. When we make general distribution, we stage the HotFix HTML page and 
the binaries subfolder to 
 using SVN 
copies.  In 24-48 hours or so that material will show up automatically on 
archive.apache.org and we can make the general distribution announcement.  The 
dist.apache.org materials can be removed when that happens.  WARNING. The 
Windows material is not ready, and some renaming will happen.  That should all 
be done by the end of Tuesday (GMT).  

  3. Next Step under Download and Installation.  The README for Windows 
addresses the way to Unzip and provides important information about how the 
extract is into a folder of a default-determined name.  I don't know if the 
others provide comparable information and/or operating from a terminal is 
assumed.

  4. How to verify the download & installation.  Verifying the Zip is 
sufficient.  The table does not identify the files those check cases are from 
so it is not at all clear what value this is.  RECOMMENDATION: If it is 
valuable, we should include the additional hashes inside the Zips, and provide 
the size and time stamp information in the individual README files.  That way 
there is no redundancy and the information is maintained in exactly one place.  

 - Dennis
  

> >
> > Thanks
> >
> > Marcus
> 
> Looks good to me.
> 
> 
> --
> Kay Schenk
> Apache OpenOffice
> 
> 
> "Things work out best for those who make
>  the best of the way things work out."
>  -- John Wooden
> 
> -
> 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: [Discuss] New template on cwiki for Release Notes

[Andrea Pescetti]

On 03/08/2016 Keith N. McKenna wrote:

Using the template facilities of the cwiki I have created a template for
creating Release Notes for AOO. It utilizes variables to fill in
repetitive entries, and instructive text to aid in writing.


Tested. It's very helpful, thank you. Automatic variables help a lot in 
avoiding errors related to copy/paste.


Regards,
  Andrea.

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

Re: Planning for emergency releases

[Andrea Pescetti]

On 10/08/2016 Patricia Shanahan wrote:

On 8/9/2016 2:41 PM, Andrea Pescetti wrote:

Patricia Shanahan wrote:

How do we go about getting trained as release manager?

By making a release, or two.

If we only do two or three releases a year, we will only be able to
train release managers are a rate of about two a year. Is that fast
enough to be able to ensure we always have a designated release manager?


We don't need 50 release managers. We need a community-wide 
understanding of various issues related to releases, so one properly 
communicated release can be enough to get many people trained. You will 
find out that most of the work cannot be documented: making a release is 
a community effort, requiring coordination and collective thinking; the 
technical/predictable part is minor.



Last time I tried finding documentation I found a lot about what steps
were needed, but very little about how to actually do the steps.


Start with the first step. Continuing this discussion just for the sake 
of talking won't help anyone. So, if you are volunteering for 
coordinating a 4.1.3 release, just start a thread about it, describe 
what you believe should go into it and what not. This may of course 
change with time; start with a reasonable assumption and then the 
release will contain something more or something less depending on what 
others do.


But again, don't worry too much about the process. A lot of people here 
are familiar with releases and may be able to help. For sure we won't 
settle on weekly releases, but on the other side we shouldn't let one 
year pass since our 4.1.2 release before making another one. (I would 
prefer to focus on 4.2.0, but that is another matter and you feel more 
confident in coordinating a 4.1.3 release I'll help you nonetheless; 
just start).


Regards,
  Andrea.

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

RE: Planning for emergency releases

[Dennis E. Hamilton]

> -Original Message-
> From: Patricia Shanahan [mailto:p...@acm.org]
> Sent: Sunday, August 14, 2016 16:28
> To: dev@openoffice.apache.org
> Subject: Re: Planning for emergency releases
> 
> On 8/12/2016 2:14 PM, Dennis E. Hamilton wrote:
> >
> >
> >> -Original Message- From: Patricia Shanahan
> >> [mailto:p...@acm.org]
> ...
> >> Personally, I would like to treat the last stable release as the
> >> base for emergency fixes. I started out suggesting using the
> >> current patch as an exercise to work through the process for doing
> >> that.
> >>
> >> However, I have seen a lot of push back on the idea of ever doing
> >> a release that only has one change.
> > [orcmid]
> >
> > Yes.  It might be necessary to do triage - choose highly-vulnerable
> > platforms, common languages, etc.
> >
> > And, if we are talking about an unpatched vulnerability with an
> > exploit in the wild, I don't think the ASF Board will be sympathetic
> > to our reticence.
> >
> > I agree that we do need to do fire drills simply to be able to
> > respond when an emergency arises.
> 
> I would prefer to see agreement within the PMC on an emergency release
> process, followed by a fire drill to test it. My understanding, from
> following bo...@apache.org, is that if the ASF Board ever gets involved,
> they will swing hammers not scalpels.
[orcmid] 

Patricia,

I agree that this is a matter for project governance.  

I suppose it is a matter of setting a policy with regard to emergency 
preparedness, having timely responses to serious defects (security 
vulnerabilities, loss-of-data crashers, corrupted operation, etc.) that deserve 
speedy remedies.  Historically, there are ways of accomplishing this from 
hotfixes for those encountering the problem to updates (less than wholesale), 
and new releases.

I think the discussion and determination can go here on dev@.  It seems like an 
appropriate major topic.

So, how can we deliberate on this and come to a conclusion as to direction and 
then execution?

 - Dennis
> 
> -
> 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: [PATCH DOWNLOAD] Draft for the hotfix webpage

[Kay sch...@apache.org]

On 08/13/2016 02:16 PM, Marcus wrote:
> As we have now the patched library file and Readme for all platforms,
> IMHO not much more is needed to go public with the hotfix. Therefore
> I've created a draft version of the hotfix download webpage:
> 
> http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/hotfix.html
> 
> Please review and tell me your feedback.
> 
> Thanks
> 
> Marcus

Looks good to me.


-- 
Kay Schenk
Apache OpenOffice


"Things work out best for those who make
 the best of the way things work out."
 -- John Wooden

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