Re: rework the automated tests to not require an office build first

2021-06-20 Thread Keith N. McKenna 
On 2021-06-12 at 9:13, Carl Marcum  wrote:
>Hi All,
>
>cc'd qa@
>
>I think it would be good to rework the test framework to not require 
>having just built the office.
>

I believe that you are right. I know for myself, I do not have the capacity to
be able to build on Windows and cannot run the automated tests.

>Currently, to compile and run the tests, there are dependencies on 
>environment settings created and files built into main/solver/.
>Mostly things like idlc, regmerge, and javamaker etc. and the UNO jar files.
>All these file dependencies are also available in either the office that 
>would be under test or the SDK.
>
>I think it would be a benefit for QA and open the use and development of 
>automated tests to testers and developers that don't also have a AOO 
>build environment.

It would definitely be a help to QA. If a volunteer does not have the capacity
to build, the most they can do is to confirm that a particular bug exists with
their OS, and then verify that a build with a specific patch fixed the
problem. With the ability to run the automated tests, individual volunteers
could contribute more than just confirming and verifying particular bugs.

>For instance I can run the test suite against Linux where I have a build 
>env but not on Windows where I don't.
>
>The one big thing about this would be it would require a tester to have 
>the SDK installed in the office under test.
>I think this is a much lower bar than building the office to get them.
>
>Does anyone have an opinion one way or the other?
>

I believe that it would be a very good idea 

Regards
Keith

>Thanks,
>Carl
>
>
>-
>To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
>For additional commands, e-mail: qa-h...@openoffice.apache.org


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

Re: New QA Volunteer

2019-03-09 Thread Keith N. McKenna 

  
  
Greetings Minu and Welcome to Apache OpenOffice;

If you have not already perused it, the QA orientation page is a good place to
start. There you will find directions on creating a Bugzilla (our
bug tracking system) Account and other information. I also strongly
suggest looking at the Level 1 and Level 2 documents on the
Orientation page as they give a good overview of how projects at the
Apache Software Foundation (ASF) operate and the common
infrastructure provided to all projects.

Regards
Keith N. McKenna

On 3/6/2019 12:25 AM, Minu wrote:


  Hi I am Minu
Would love to be a part of QA Volunteers team at Apache OpenOffice Software.
I am from Atlanta, GA, USA
Want to pursue my career as a QA.
I hope i will learn and also contribute to this work with my best efforts.

Thanks
Minu




  




signature.asc
Description: OpenPGP digital signature

Re: intoduction

2019-01-07 Thread Keith N. McKenna 
On 12/31/2018 7:18 AM, Anastasiya Porokhnia wrote:
> Hi, I am Anastasiia!  I was born in Ukraine, but now I live in Israel.  I
> have finished  to study QA  so I want to help you as volunteer to make your
> products better. I use your product- Jmeter in my work. But i prefer to
> test functionality and GUI. But i open for something new! I also want to do
> this:
>
>- Work on bug reports and try to reproduce them
>
>  Anyway, I am waiting for your answer with exciting!
Greetings Anastasia and Welcome to Apache OpenOffice (AOO);

For an overview of our QA process please see the orientation page at
http://openoffice.apache.org/orientation/intro-qa.html.

Regards
Keith N. McKenna




signature.asc
Description: OpenPGP digital signature

Re: Many manual test cases now available

2018-06-19 Thread Keith N. McKenna 
Hi again Kay... see below

On 6/17/2018 5:19 PM, Kay Schenk wrote:
> Hi again...see below
>
> On 06/12/2018 08:50 AM, Keith N. McKenna wrote:
>> On 6/11/2018 5:09 PM, Kay Schenk wrote:
>>> On 06/11/2018 09:24 AM, Keith N. McKenna wrote:
>>>> On 6/9/2018 1:20 PM, Kay Schenk wrote:
>>>>> Keith, short update -- see below
>>>>>
>>>>> 
>>>>>
>>>>> ​T
>>>>> hmmm...well the Impress directory itself is NOT showing up on the
>>>>> staging server, so this IS a problem. You just need to add the
>>>>> directories themselves to svn and commit.
>>>>>
>>>>> I'm finding that adding the directories to the index script is not as
>>>>> simple as I thought it would be, but I am working on it. (grrr! why does
>>>>> stuff work on the command line but not inside a script!) My time is
>>>>> quite limited for the rest of the week, so maybe in a week or so.
>>>>>
>>>>> Take care.
I added and committed the directories. The Impress directory and one
sub-directory  did show up in the staging area. I believe the reason was
that the sub-directory did have some files in it whereas the other did
not.  However when published it once again get the You don't have
permission to access /QA/testcase/ManualTesting/ on this server. It is
however still fine on the staging area.

Regards
Keith
>>>>>
>>> On the other (my) issue about index.html NOT being removed. I did verify
>>> on staging that the index.html had been removed reverting to the
>>> "default" setup on that server of just displaying a file listing, before
>>> I did the publish. In any case, maybe just as well the index.html is
>>> STILL there in production otherwise we may have gotten teh "forbidden"
>>> message for the whole directory.
>>>
>>> I should have time to make changes to accommodate directory structures
>>> in the index generation script, in:
>>>
>>> https://svn.apache.org/repos/asf/openoffice/devtools/scripts/auto-index.sh
>>>
>>> in the next day or so. Since we have no dynamic mechanisms available for
>>> dynamic server-side page generation, the index will need to be
>>> regenerated whenever changes are made to this area.
>>>
>>>
>>>>> ​
>>>>>
>>>>>
>>>>>> ​
>>>>>>
>>>>>>> BTW I see that you use a PGP key to sign the e-mails but it has never
>>>>>>> been uploaded to a key server. If you send me the public key I will add
>>>>>>> it to my keyring.
>>>>>>>
>>>>>> ​Normally, my PGP key is not in use. It gets requested in Thunderbird 
>>>>>> when
>>>>>> I respond to a "signed" message like yours.
>>>>>> ​
>>>>>>
>>>>>>
>>>>>>> Regards
>>>>>>> Keith
>>>>>>>> If you did, then I'll need to modify my little index creation creation
>>>>>>>> script to pull in your additions likely this weekend sometime.
>>>>>>>> Thanks so much for your work on this,
>>>>>>>>
>>>>>> --
>>>>>> --
>>>>>> MzK
>>>>>>
>>>>>> "Less is MORE."
>>>>>>
>>




signature.asc
Description: OpenPGP digital signature

Re: Many manual test cases now available

2018-06-17 Thread Keith N. McKenna 
Response inline

On 6/17/2018 5:19 PM, Kay Schenk wrote:
> Hi again...see below
>
> On 06/12/2018 08:50 AM, Keith N. McKenna wrote:
>> On 6/11/2018 5:09 PM, Kay Schenk wrote:
>>> On 06/11/2018 09:24 AM, Keith N. McKenna wrote:
>>>> On 6/9/2018 1:20 PM, Kay Schenk wrote:
>>>>> Keith, short update -- see below
>>>>>
>>>>> 
>>>>>
>>>>> ​This deletion did not seem to "take" in publishing. So, for now, things
>>>>> look as they did. Your new Impress area is there, but the index.html file
>>>>> needs to be regenerated.
>>>> On further study there may be a couple of mistakes on my part due to my
>>>> unfamiliarity with SVN that may have contributed to this problem.
>>>>
>>>>  1. I did not do a specific add of the directories before committing them.
>>>>  2. I use Tortoise SVN and I vaguely remember something about the repos
>>>> having difficulty with Windows line endings
>>>>
>>>>  If either of these could be contributing I can do the add for the
>>>> directories and try the commit again. Also Tortoise SVN  now has an EOL
>>>> property that also to specifically set the EOL type to be used. I can
>>>> also try setting those directories to specifically use Linux EOL's if
>>>> y'all think that might help.
>>>>
>>>> Regards
>>>> Keith
>>> From what I can see right now, #1 is not a problem. When I did an svn
>>> update, everything cam through OK.
>> The only potential downfall is that even after an SVN update they are
>> still showing as unversioned in my working copy. As the initial commit
>> was only to evaluate a more detailed structure it isn't a problem for now.
>>
>> Keith
> hmmm...well the Impress directory itself is NOT showing up on the
> staging server, so this IS a problem. You just need to add the
> directories themselves to svn and commit.
>
> I'm finding that adding the directories to the index script is not as
> simple as I thought it would be, but I am working on it. (grrr! why does
> stuff work on the command line but not inside a script!) My time is
> quite limited for the rest of the week, so maybe in a week or so.
>
> Take care.
> Kay;
Just got home from a motorcycle ride to my better half's. Will do the
add and re-commit after I do dishes.

Take Care
Keith
>>> On the other (my) issue about index.html NOT being removed. I did verify
>>> on staging that the index.html had been removed reverting to the
>>> "default" setup on that server of just displaying a file listing, before
>>> I did the publish. In any case, maybe just as well the index.html is
>>> STILL there in production otherwise we may have gotten teh "forbidden"
>>> message for the whole directory.
>>>
>>> I should have time to make changes to accommodate directory structures
>>> in the index generation script, in:
>>>
>>> https://svn.apache.org/repos/asf/openoffice/devtools/scripts/auto-index.sh
>>>
>>> in the next day or so. Since we have no dynamic mechanisms available for
>>> dynamic server-side page generation, the index will need to be
>>> regenerated whenever changes are made to this area.
>>>
>>>
>>>>> ​
>>>>>
>>>>>
>>>>>> ​
>>>>>>
>>>>>>> BTW I see that you use a PGP key to sign the e-mails but it has never
>>>>>>> been uploaded to a key server. If you send me the public key I will add
>>>>>>> it to my keyring.
>>>>>>>
>>>>>> ​Normally, my PGP key is not in use. It gets requested in Thunderbird 
>>>>>> when
>>>>>> I respond to a "signed" message like yours.
>>>>>> ​
>>>>>>
>>>>>>
>>>>>>> Regards
>>>>>>> Keith
>>>>>>>> If you did, then I'll need to modify my little index creation creation
>>>>>>>> script to pull in your additions likely this weekend sometime.
>>>>>>>> Thanks so much for your work on this,
>>>>>>>>
>>>>>> --
>>>>>> --
>>>>>> MzK
>>>>>>
>>>>>> "Less is MORE."
>>>>>>
>>




signature.asc
Description: OpenPGP digital signature

Re: Many manual test cases now available

2018-06-12 Thread Keith N. McKenna 
On 6/11/2018 5:09 PM, Kay Schenk wrote:
>
> On 06/11/2018 09:24 AM, Keith N. McKenna wrote:
>> On 6/9/2018 1:20 PM, Kay Schenk wrote:
>>> Keith, short update -- see below
>>>
>>> 
>>>
>>> ​This deletion did not seem to "take" in publishing. So, for now, things
>>> look as they did. Your new Impress area is there, but the index.html file
>>> needs to be regenerated.
>> On further study there may be a couple of mistakes on my part due to my
>> unfamiliarity with SVN that may have contributed to this problem.
>>
>>  1. I did not do a specific add of the directories before committing them.
>>  2. I use Tortoise SVN and I vaguely remember something about the repos
>> having difficulty with Windows line endings
>>
>>  If either of these could be contributing I can do the add for the
>> directories and try the commit again. Also Tortoise SVN  now has an EOL
>> property that also to specifically set the EOL type to be used. I can
>> also try setting those directories to specifically use Linux EOL's if
>> y'all think that might help.
>>
>> Regards
>> Keith
> From what I can see right now, #1 is not a problem. When I did an svn
> update, everything cam through OK.
The only potential downfall is that even after an SVN update they are
still showing as unversioned in my working copy. As the initial commit
was only to evaluate a more detailed structure it isn't a problem for now.

Keith
>
> On the other (my) issue about index.html NOT being removed. I did verify
> on staging that the index.html had been removed reverting to the
> "default" setup on that server of just displaying a file listing, before
> I did the publish. In any case, maybe just as well the index.html is
> STILL there in production otherwise we may have gotten teh "forbidden"
> message for the whole directory.
>
> I should have time to make changes to accommodate directory structures
> in the index generation script, in:
>
> https://svn.apache.org/repos/asf/openoffice/devtools/scripts/auto-index.sh
>
> in the next day or so. Since we have no dynamic mechanisms available for
> dynamic server-side page generation, the index will need to be
> regenerated whenever changes are made to this area.
>
>
>>> ​
>>>
>>>
>>>> ​
>>>>
>>>>> BTW I see that you use a PGP key to sign the e-mails but it has never
>>>>> been uploaded to a key server. If you send me the public key I will add
>>>>> it to my keyring.
>>>>>
>>>> ​Normally, my PGP key is not in use. It gets requested in Thunderbird when
>>>> I respond to a "signed" message like yours.
>>>> ​
>>>>
>>>>
>>>>> Regards
>>>>> Keith
>>>>>> If you did, then I'll need to modify my little index creation creation
>>>>>> script to pull in your additions likely this weekend sometime.
>>>>>> Thanks so much for your work on this,
>>>>>>
>>>>>
>>>> --
>>>> --
>>>> MzK
>>>>
>>>> "Less is MORE."
>>>>
>>>
>>




signature.asc
Description: OpenPGP digital signature

Re: Many manual test cases now available

2018-06-11 Thread Keith N. McKenna 

On 6/9/2018 1:20 PM, Kay Schenk wrote:
> Keith, short update -- see below
>
> 
>
> ​This deletion did not seem to "take" in publishing. So, for now, things
> look as they did. Your new Impress area is there, but the index.html file
> needs to be regenerated.
On further study there may be a couple of mistakes on my part due to my
unfamiliarity with SVN that may have contributed to this problem.

 1. I did not do a specific add of the directories before committing them.
 2. I use Tortoise SVN and I vaguely remember something about the repos
having difficulty with Windows line endings

 If either of these could be contributing I can do the add for the
directories and try the commit again. Also Tortoise SVN  now has an EOL
property that also to specifically set the EOL type to be used. I can
also try setting those directories to specifically use Linux EOL's if
y'all think that might help.

Regards
Keith
> ​
>
>
>> ​
>>
>>> BTW I see that you use a PGP key to sign the e-mails but it has never
>>> been uploaded to a key server. If you send me the public key I will add
>>> it to my keyring.
>>>
>> ​Normally, my PGP key is not in use. It gets requested in Thunderbird when
>> I respond to a "signed" message like yours.
>> ​
>>
>>
>>> Regards
>>> Keith
 If you did, then I'll need to modify my little index creation creation
 script to pull in your additions likely this weekend sometime.
 Thanks so much for your work on this,

>>>
>>>
>>
>> --
>> --
>> MzK
>>
>> "Less is MORE."
>>
>
>




signature.asc
Description: OpenPGP digital signature

Re: Many manual test cases now available

2018-06-08 Thread Keith N. McKenna 
On 6/8/2018 12:54 PM, Kay Schenk wrote:
> On 06/07/2018 12:41 PM, Keith N. McKenna wrote:
>> On 5/7/2018 12:48 PM, Kay Schenk wrote:
>>> On Sun, May 6, 2018 at 3:48 PM, Keith N. McKenna 
>>> wrote:
>>>
>>>> On 5/3/2018 12:19 PM, Kay Schenk wrote:
>>>>> On 05/02/2018 11:05 AM, Keith N. McKenna wrote:
>>>>>> On 4/25/2018 3:59 PM, Kay Schenk wrote:
>>>>>>> On 04/24/2018 03:25 PM, Keith N. McKenna wrote:
>>>>>>>> On 4/18/2018 6:22 PM, Kay Schenk wrote:
>>>>>>>> 
>>>>>> I think the first level of organization should be by application
>>>>>>>> (Writer, Calc, etc).  After that It will depend on how we want to use
>>>>>>>> them.My preference would be to break them down into finer grained
>>>> units
>>>>>>>> that people could volunteer to execute.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Keith
>>>>>>> Organizing the cases with respect to AOO module -- Writer, Calc, etc.
>>>> --
>>>>>>> sounds ideal.
>>>>>>>
>>>>>>> Do we have any ideas for how to perform this classification?
>>>>>> What I have done with the Impress ones was to use the same folder
>>>>>> structure as that used on the TestLink site. that way I can fit them
>>>>>> into whatever structure we decide upon. At this point you would either
>>>>>> have to open every file and hope the description either tells you are
>>>>>> can be easily derived, or manually go through the directory structure on
>>>>>> the TestLink site and match the test numbers.
>>>>> That's great Keith. I realize now in hindsight that I should have done
>>>>> this as well. :(
>>>>> I can go back and do this but it will take some time given my current
>>>>> personal schedule.
>>>>>
>>>>> Would it be possible for you to set up an area under --
>>>>> https://www.openoffice.org/qa/testcase/ManualTesting/
>>>>>
>>>>> and just use your structure so we can take a look?
>>>> Kay;
>>>> I can do that later in the week, but understand that the structure was
>>>> somewhat different for each application depending on the internals of
>>>> the application. For example Impress has a lot of tests for different
>>>> type of animations where I do not believe Writer uses them much at all.
>>>>
>>> ​The organizational structure used for the test case setup seemed mostly to
>>> be dependent on what the QA folks thought needed to be tested at the time
>>> which is why ​
>>>
>>> ​I didn't put all that much effort into keeping it the way it was on
>>> TestLInk.
>>>
>>> ​
>>>
>>>> I will try to comit my Impress structure later in the week. I am busy
>>>> with Dr. appointments the bigining of the week.
>>>>
>>> ​Sounds good!
>> Kay; I committed the Directory Structure I used for impress files to the
>> ManualTest directory. It appeared to build but they do not show on the
>> production website. Is there something else I should have changed?
>>
>> Sorry for taking so long, but with medical issues with my girlfriend and
>> some personal issues of my own the last month has been hectic.
>>
>> Regards
>> Keith
> Hi Keith --
> No worries. I'll take a look. Did you "publish" your changes after
> committing?
No was not aware of that step or how to do it. I rarely use my committer
privileges as I am not a coder in any way shape or form. I used to use
the cms to make minor changes to the aoo site but that no longer appears
to work. If you do not mind giving me a quick rundown on how I will be
glad to do that in the future.

BTW I see that you use a PGP key to sign the e-mails but it has never
been uploaded to a key server. If you send me the public key I will add
it to my keyring.

Regards
Keith
> If you did, then I'll need to modify my little index creation creation
> script to pull in your additions likely this weekend sometime.
> Thanks so much for your work on this,
>
>>




signature.asc
Description: OpenPGP digital signature

Re: Many manual test cases now available

2018-06-07 Thread Keith N. McKenna 
On 5/7/2018 12:48 PM, Kay Schenk wrote:
> On Sun, May 6, 2018 at 3:48 PM, Keith N. McKenna 
> wrote:
>
>> On 5/3/2018 12:19 PM, Kay Schenk wrote:
>>> On 05/02/2018 11:05 AM, Keith N. McKenna wrote:
>>>> On 4/25/2018 3:59 PM, Kay Schenk wrote:
>>>>> On 04/24/2018 03:25 PM, Keith N. McKenna wrote:
>>>>>> On 4/18/2018 6:22 PM, Kay Schenk wrote:
>>>>>> 
>>>> I think the first level of organization should be by application
>>>>>> (Writer, Calc, etc).  After that It will depend on how we want to use
>>>>>> them.My preference would be to break them down into finer grained
>> units
>>>>>> that people could volunteer to execute.
>>>>>>
>>>>>> Regards
>>>>>> Keith
>>>>> Organizing the cases with respect to AOO module -- Writer, Calc, etc.
>> --
>>>>> sounds ideal.
>>>>>
>>>>> Do we have any ideas for how to perform this classification?
>>>> What I have done with the Impress ones was to use the same folder
>>>> structure as that used on the TestLink site. that way I can fit them
>>>> into whatever structure we decide upon. At this point you would either
>>>> have to open every file and hope the description either tells you are
>>>> can be easily derived, or manually go through the directory structure on
>>>> the TestLink site and match the test numbers.
>>> That's great Keith. I realize now in hindsight that I should have done
>>> this as well. :(
>>> I can go back and do this but it will take some time given my current
>>> personal schedule.
>>>
>>> Would it be possible for you to set up an area under --
>>> https://www.openoffice.org/qa/testcase/ManualTesting/
>>>
>>> and just use your structure so we can take a look?
>> Kay;
>> I can do that later in the week, but understand that the structure was
>> somewhat different for each application depending on the internals of
>> the application. For example Impress has a lot of tests for different
>> type of animations where I do not believe Writer uses them much at all.
>>
>
> ​The organizational structure used for the test case setup seemed mostly to
> be dependent on what the QA folks thought needed to be tested at the time
> which is why ​
>
> ​I didn't put all that much effort into keeping it the way it was on
> TestLInk.
>
> ​
>
>> I will try to comit my Impress structure later in the week. I am busy
>> with Dr. appointments the bigining of the week.
>>
> ​Sounds good!
Kay; I committed the Directory Structure I used for impress files to the
ManualTest directory. It appeared to build but they do not show on the
production website. Is there something else I should have changed?

Sorry for taking so long, but with medical issues with my girlfriend and
some personal issues of my own the last month has been hectic.

Regards
Keith




signature.asc
Description: OpenPGP digital signature

Re: Many manual test cases now available

2018-05-02 Thread Keith N. McKenna 
On 4/25/2018 3:59 PM, Kay Schenk wrote:
> On 04/24/2018 03:25 PM, Keith N. McKenna wrote:
>> On 4/18/2018 6:22 PM, Kay Schenk wrote:
>> 
I think the first level of organization should be by application
>> (Writer, Calc, etc).  After that It will depend on how we want to use
>> them.My preference would be to break them down into finer grained units
>> that people could volunteer to execute.
>>
>> Regards
>> Keith
> Organizing the cases with respect to AOO module -- Writer, Calc, etc. --
> sounds ideal.
>
> Do we have any ideas for how to perform this classification?
What I have done with the Impress ones was to use the same folder
structure as that used on the TestLink site. that way I can fit them
into whatever structure we decide upon. At this point you would either
have to open every file and hope the description either tells you are
can be easily derived, or manually go through the directory structure on
the TestLink site and match the test numbers.

I believe that a deeper level of granularity is needed that just the
application.

Regards
Keith





signature.asc
Description: OpenPGP digital signature

Many manual test cases now available

2018-04-24 Thread Keith N. McKenna 
On 4/18/2018 6:22 PM, Kay Schenk wrote:
> Many of the old TestLink test cases are now available (along with others)
> from the QA web area --
>
> https://www.openoffice.org/qa/testcase/index.html
>
> We could certainly use some feedback on them with respect to:
>
> * usefulness -- what to keep, what to discard
> * organization -- can you help with organizing these cases into categories
I think the first level of organization should be by application
(Writer, Calc, etc).  After that It will depend on how we want to use
them.My preference would be to break them down into finer grained units
that people could volunteer to execute.

Regards
Keith
> * clarity -- are the instruction understandable, etc.
>
> More former TestLink cases will be ported soon.
>
> There are other older cases available from this area as well.
>
> Happy testing!
>




signature.asc
Description: OpenPGP digital signature

Re: Need HELP! with brute force extraction of TestLink cases...

2018-02-12 Thread Keith N. McKenna 
Starting Impress/Header and Footer

On 2/12/2018 5:08 PM, Kay Schenk wrote:
> Hello all--
>
> After working on saving some of our case on the now mostly
> inaccessible TestLink instance, I'm sending out a HELP message!
> Extractions can be done with a guest account.
>
> If you go to:
>
> http://aootesting.adfinis-sygroup.org/login.php?note=expired
> 
>
> you can apply for a guest account. After that, once you log in, you
> will see 2 test "projects" related to Apache OpenOffice -- Apache
> OpenOffice testproject (the main one) and, Apache OpenOffice
> testproject2 (mostly Mac related).
>
> Currently, I have finished extracting cases through the section
> entitled --
> AOO Calc (220) and am going to start on Fidelity (255). We could use
> some additional help on extracting cases in sections past Fidelity --
> Drawing, Impress, Installation, Sidebar, etc.
>
> If you want to help with case extractions, here are further instructions.
>
> 1. Choose "Apache OpenOffice testproject", then "Browse Test Cases"
> from the left menu, you will see a tree of test cases (toward the
> bottom of the page and attached to this message).
> Note the total number is 1690. Yes, that's a lot. The number next to
> each element in the tree is the number of cases in a given sub-section.
>
> 2. Continually expanding each subsection will finally lead to
> individual test case descriptions/instructions. Clicking on an
> individual "case" brings up the actual text of the case (most of the
> time) along with a "Print View" option for each case.
>
> 3. Use the Print View option to save each case somewhere on your system.
>
> We will need to discuss further what to do with these  at some point.
>
> And, if you find a better way to do this -- please let us know.
>
>
> -- 
> --
> MzK
>
> "Ring out the false, ring in the true."
>  -- poem "In Memoriam", Alfred Lord Tennyson
>
>
> -
> To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: qa-h...@openoffice.apache.org




signature.asc
Description: OpenPGP digital signature

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

2016-08-19 Thread Keith N. McKenna 
Dennis E. Hamilton wrote:
>
>> -Original Message-
>> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
>> Sent: Thursday, August 18, 2016 14:46
>> To: qa@openoffice.apache.org; d...@openoffice.apache.org
>> Subject: Re: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
>>
> [ ... ]
>> [knmc]
>> As we move forward to a general distribution here  is an odt revision of
>> the readme that can be used to generate an html, pdf, or text versions.
>> All versions are attached but may not come through to the list. They can
>> all be accessed from the following link.
>> <https://1drv.ms/f/s!AMMYmStvrJNJgQQ>
>> All feedback is both welcomed and encouraged.
> [orcmid] 
>
> The .odt and the .txt file come through as attachments.
>
> Do you have specific recommendations about what should be done with these?  
[knmc]
My initial idea was to create a template that could be used to
standardize this type of documentation rather than having individuals
using different tools and methodologies on the different operating
systems that we support. It just took me longer than I had expected.
At this point it is far to late to attempt to do anything for this
particular patch release. So all I am looking for is feed back on
structure and if it is even a worthwhile endeavor to pursue.
[knmc]
> I notice that there are problems with the .txt file layout not having hard 
> line breaks.
[knmc]
That is one reason I have never been a big fan of using plain text for
documentation. I would rather see PDF or HTML
>   The name changes and dates in 0.2.0 are not reflected.
That is just a field and can be changed easily
>   The .odt also needs layout work.  There's too much white space and I have 
> not looked closely enough to figure out why.
[knmc]
I suspect that it is due to the styles choices I made. I based them off
the standard headings and text styles. I do not see to much white space
, but that may be a difference on how we view document structure.
>
> I know we differ on formatting and some document organization matters.  I am 
> not going to address them at this point.
There are always going to be those kinds of differences and compromises
have to be made on all sides. That is why I am seeking feedback.
> I am going to 1.0.0 now, essentially with the 0.2.0 except for the change of 
> version number and removal of the limitation to testing use.  I did the other 
> repair you suggested.  I think Marcus is ready on the other binaries, so 
> something will happen tomorrow (Friday).  
Given the time critical nature it is imperative that the general release
be done quickly. As I said earlier it took me longer than I had
anticipated to get the structure to where I wanted it.

Regards
Keith
>
> I'm not certain what the final inch is just yet, but it looks like everything 
> is ready enough.
>
>  - Dennis
>> regards
>> Keith
>>>
>>> -
>>> To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: qa-h...@openoffice.apache.org
>>>
>
>
> -
> To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: qa-h...@openoffice.apache.org
>




signature.asc
Description: OpenPGP digital signature

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

2016-08-18 Thread Keith N. McKenna 
Dennis E. Hamilton wrote:
>
>> -Original Message-
>> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
>> Sent: Monday, August 15, 2016 21:05
>> To: qa@openoffice.apache.org; d...@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
>>>
>>> <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
>> 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
>>>
> [ ... ]
[knmc]
As we move forward to a general distribution here  is an odt revision of
the readme that can be used to generate an html, pdf, or text versions.
All versions are attached but may not come through to the list. They can
all be accessed from the following link.
<https://1drv.ms/f/s!AMMYmStvrJNJgQQ>
All feedback is both welcomed and encouraged.

regards
Keith
>
>
> -
> To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: qa-h...@openoffice.apache.org
>



New_Readmeforpatch.odt
Description: application/vnd.oasis.opendocument.text
Title: Readme




APPLYING
HOTFIX FOR APACHE OPENOFFICE ON WINDOWS

README-4.1.2-patch1-apply-Windows.txt	1.0.0	2016-08-07

	
		
		Table of
		Contents
	
	Notice	1
	Purpose	1
	Intended
	Audience	1
	Prerequisites	2
	Preliminary
	Instructions	2
	Apply Patch
	Automatically	3
	Removing the Patch	3
	Appendicies	4
	Manually
	Apply Patch	4
	Troubleshooting	4




Notice
Licensed to the Apache Software
Foundation (ASF) under one or more contributor license agreements.
The ASF licenses this file to you under the Apache License, Version
2.0 (the "License"). You may obtain a copy of the License
at http://www.apache.org/licenses/LICENSE-2.0
Purpose
The purpose of this document is to
describe how to apply the hotfix to eliminate a security
vulnerability identified as CVE-2016-1513. The latest details about
that vulnerability and its mitigation can be found on the web at
<http://www.openoffice.org/security/cves/CVE-2016-1513.html>.
The hotfix is provided as a zip
file at the following
location:<https://dist.apache.org/repos/dist/release/openoffice/4.1.2-patch1/>

Intended Audience
This document is primarily
intended for use by non-technical individuals but presumes
familiarity with the following;

	Your account has
	administrator privileges or you have access to an adminstrator
	password
	NOTE: If your Operating System
	is Windows XP you must be logged into an account with administrator
	privileges.
	Use of a web browser to
	download files from the internet
	Use of the file manager to
	locate files and folders
	Use of the file manager to
	select files

Prerequisites

	Apache OpenOffice Version
	4.1.2 
	
	Quickstarter must be off

Preliminary
Instructions

	Verify installed version is
	4.1.2
	
		Open Apache OpenOffice 
		
	
	Download the zip file from
	<https://dist.apache.org/repos/dist/release/openoffice/4.1.2-patch1/>
	
		Use of the download folder
		for this procedure is fine
	
	Navigate to the above folder
	with the file manager
	Select the downloaded zip
	file
	Right click the zip file
	Select Extract All... from
	the context menu
	
		This will create a folder in
		the same folder you downloaded the archive with the contents of the
		archive un-packed in it
	
	Open the new folder from step
	5 it should contain the following files
	
		README-4.1.2-patch1-apply-Windows.txt
		
			This procedure
		
		LICENSE.txt
		
			The Apache License Version
			2.0 under which the .zip and i

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

2016-08-15 Thread 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: d...@openoffice.apache.org
>> Cc: qa@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: d...@openoffice.apache.org
>>> Cc: qa@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: d...@openoffice.apache.org
 Cc: qa@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

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

2016-08-13 Thread Keith N. McKenna 
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

Dennis E. Hamilton wrote:
>
>> -Original Message-
>> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
>> Sent: Friday, August 12, 2016 13:49
>> To: qa@openoffice.apache.org; d...@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
> [orcmid] 
>
> Thanks Keith.  The copy-paste error in the APPLY :FAIL3 message will be 
> fixed.  Thanks for being so attentive and meticulous.  Your test log is 
> wonderful.
>
>  I'm gratified that the Administrator Permissions pain has been alleviated on 
> both admin and standard Windows 7 accounts.
>
> I look forward to anything else you come up with.  I anticipate that we can 
> go to 1.0.0 for the next round and make general availability next week.
>
>  - Dennis
>>
>> Dennis E. Hamilton wrote:
>>
>>
>>  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
>>  <http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
>> patch1/binaries/Windows>
>> <http://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
>> patch1/binaries/Windows> .
>>
>>   - Dennis
> [ ... ]
>
>
>
> -
> To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: qa-h...@openoffice.apache.org
>



README-4.1.2-patch1-apply-Windows.odt
Description: application/vnd.oasis.opendocument.text


signature.asc
Description: OpenPGP digital signature