Re: [WEBSITE] QA area changes, and differences between staging and production
On 4/2/2018 8:07 PM, Keith N. McKenna wrote: > On 4/2/2018 7:29 PM, Kay Schenk wrote: >> OK, I think the filenames are fixed now. Bad commit the first time I guess. >> Great if you could help with the restructuring. Please keep in mind that >> this is not ALL the TestLink files. I need to see what we're missing and >> want to have at this point. >> > Thanks Kay. Doing a new checkout now. Hopefully this should do it. Will > let you know the outcome. > > Keith > Checkout completed with no errors. Thank you very much for your assistance. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [WEBSITE] QA area changes, and differences between staging and production
On 4/2/2018 7:29 PM, Kay Schenk wrote: > OK, I think the filenames are fixed now. Bad commit the first time I guess. > Great if you could help with the restructuring. Please keep in mind that > this is not ALL the TestLink files. I need to see what we're missing and > want to have at this point. > Thanks Kay. Doing a new checkout now. Hopefully this should do it. Will let you know the outcome. Keith - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [WEBSITE] QA area changes, and differences between staging and production
On Mon, Apr 2, 2018 at 4:18 PM, Keith N. McKennawrote: > On 4/2/2018 6:41 PM, Kay Schenk wrote: > > On Mon, Apr 2, 2018 at 3:07 PM, Keith N. McKenna < > keith.mcke...@comcast.net> > > wrote: > > > >> On 3/30/2018 3:15 PM, Kay Schenk wrote: > >>> I've committed changes to the QA area complete with the "index" > >> capability > >>> of the new test case area. I'll be working on additional changes to the > >> QA > >>> area over the next few days before a general announcement to QA. > >>> > >>> NOTE: the staging web site -- http://ooo-site.staging.apache.org/ -- > >> allows > >>> for +Indexes automatically so displays can be misleading in that > >>> environment. Our default setup for -- http://www.openoffice.org/ -- > does > >>> not. > >>> > >>> We should probably request that infra setup both these servers the > same. > >>> > >>> > >> Kay; > >> > >> Just tried to check out ooo-site repo in preparation for completing the > >> download of all the Impress test cases and ran into a problem. You have > >> a number of files that include an * in the filename. This is no-no on > >> windows and causes a corrupt working copy on Windows that can not be > >> used. Can you update the ooo-site repo and replace those 1/2 dozen or so > >> files with * in the names so that I can check out a new working copy? > >> > > > > Yes, I will do that. > Thanks Kay. A closer look at the repo shows somewhere around 2 dozen > files that have * in the file name. > > > > > > > > >> > >> Also a process question. Why did you chose to put all the tests in a > >> single directory rather than breaking it down by application the way > >> they were on the testlink site? > > > > > > An oversight on my part, but as I got into this, I did see there was a > LOT > > of overlap, with the former QA folks establishing categories for some > very > > specific areas. We can probably restructure this new area just based on > > file names and move things around. I discovered on the original TestLink > > site that there were MANY fine-grained categorizations that we probably > > don't need. > > > > > > > > > >> The process engineer in me says that it > >> would be cleaner to do it by application so that a volunteer working on > >> Writer doesn't have to wade through tests that do not apply to them to > >> find the Writer specific ones. > >> > > > > I thought perhaps the file names themselves would suffice for > determining > > categories. In any case, please feel free to organize this area further. > I > > would think subareas for Wrtier, Calc, Impress, Database, Drawing would > be > > enough -- or not. > > Once I get a clean checkout of the repo I will take a closer look at > possibilities for restructuring it a bit. > OK, I think the filenames are fixed now. Bad commit the first time I guess. Great if you could help with the restructuring. Please keep in mind that this is not ALL the TestLink files. I need to see what we're missing and want to have at this point. > > Regards > Keith > > > > > > > >> > >> Regards > >> Keith > > > > > >> > >> > > > -- -- MzK "Less is MORE."
Re: [WEBSITE] QA area changes, and differences between staging and production
On 4/2/2018 6:41 PM, Kay Schenk wrote: > On Mon, Apr 2, 2018 at 3:07 PM, Keith N. McKenna> wrote: > >> On 3/30/2018 3:15 PM, Kay Schenk wrote: >>> I've committed changes to the QA area complete with the "index" >> capability >>> of the new test case area. I'll be working on additional changes to the >> QA >>> area over the next few days before a general announcement to QA. >>> >>> NOTE: the staging web site -- http://ooo-site.staging.apache.org/ -- >> allows >>> for +Indexes automatically so displays can be misleading in that >>> environment. Our default setup for -- http://www.openoffice.org/ -- does >>> not. >>> >>> We should probably request that infra setup both these servers the same. >>> >>> >> Kay; >> >> Just tried to check out ooo-site repo in preparation for completing the >> download of all the Impress test cases and ran into a problem. You have >> a number of files that include an * in the filename. This is no-no on >> windows and causes a corrupt working copy on Windows that can not be >> used. Can you update the ooo-site repo and replace those 1/2 dozen or so >> files with * in the names so that I can check out a new working copy? >> > > Yes, I will do that. Thanks Kay. A closer look at the repo shows somewhere around 2 dozen files that have * in the file name. > > > >> >> Also a process question. Why did you chose to put all the tests in a >> single directory rather than breaking it down by application the way >> they were on the testlink site? > > > An oversight on my part, but as I got into this, I did see there was a LOT > of overlap, with the former QA folks establishing categories for some very > specific areas. We can probably restructure this new area just based on > file names and move things around. I discovered on the original TestLink > site that there were MANY fine-grained categorizations that we probably > don't need. > > > > >> The process engineer in me says that it >> would be cleaner to do it by application so that a volunteer working on >> Writer doesn't have to wade through tests that do not apply to them to >> find the Writer specific ones. >> > > I thought perhaps the file names themselves would suffice for determining > categories. In any case, please feel free to organize this area further. I > would think subareas for Wrtier, Calc, Impress, Database, Drawing would be > enough -- or not. Once I get a clean checkout of the repo I will take a closer look at possibilities for restructuring it a bit. Regards Keith > > > >> >> Regards >> Keith > > >> >> >> - >> 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: [WEBSITE] QA area changes, and differences between staging and production
a followup, see below... On Mon, Apr 2, 2018 at 3:41 PM, Kay Schenkwrote: > > > On Mon, Apr 2, 2018 at 3:07 PM, Keith N. McKenna < > keith.mcke...@comcast.net> wrote: > >> On 3/30/2018 3:15 PM, Kay Schenk wrote: >> > I've committed changes to the QA area complete with the "index" >> capability >> > of the new test case area. I'll be working on additional changes to the >> QA >> > area over the next few days before a general announcement to QA. >> > >> > NOTE: the staging web site -- http://ooo-site.staging.apache.org/ -- >> allows >> > for +Indexes automatically so displays can be misleading in that >> > environment. Our default setup for -- http://www.openoffice.org/ -- >> does >> > not. >> > >> > We should probably request that infra setup both these servers the same. >> > >> > >> Kay; >> >> Just tried to check out ooo-site repo in preparation for completing the >> download of all the Impress test cases and ran into a problem. You have >> a number of files that include an * in the filename. This is no-no on >> windows and causes a corrupt working copy on Windows that can not be >> used. Can you update the ooo-site repo and replace those 1/2 dozen or so >> files with * in the names so that I can check out a new working copy? >> > > Yes, I will do that. > OK, I did a series of svn mv on the "bad" file names. My svn commands told me this -- some area// svn mv 350_Extend_Text_*_Cell_Properties_Numbers_Thousands_separator.html 350_Extend_Text_Cell_Properties_Numbers_Thousands_separator.html A 350_Extend_Text_Cell_Properties_Numbers_Thousands_separator.html D 350_Extend_Text_*_Cell_Properties_Numbers_Thousands_separator.html which should have deleted the old file and replaced/renamed it with the old file. However, when I did the commit, the old file names are STILL there in staging, so perhaps I need to do more to get things in sync. Later... > > >> >> Also a process question. Why did you chose to put all the tests in a >> single directory rather than breaking it down by application the way >> they were on the testlink site? > > > An oversight on my part, but as I got into this, I did see there was a > LOT of overlap, with the former QA folks establishing categories for some > very specific areas. We can probably restructure this new area just based > on file names and move things around. I discovered on the original TestLink > site that there were MANY fine-grained categorizations that we probably > don't need. > > > > >> The process engineer in me says that it >> would be cleaner to do it by application so that a volunteer working on >> Writer doesn't have to wade through tests that do not apply to them to >> find the Writer specific ones. >> > > I thought perhaps the file names themselves would suffice for determining > categories. In any case, please feel free to organize this area further. I > would think subareas for Wrtier, Calc, Impress, Database, Drawing would be > enough -- or not. > > > >> >> Regards >> Keith > > >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> > > > -- > -- > MzK > > "Less is MORE." > -- -- MzK "Less is MORE."
Re: [WEBSITE] QA area changes, and differences between staging and production
On Mon, Apr 2, 2018 at 3:07 PM, Keith N. McKennawrote: > On 3/30/2018 3:15 PM, Kay Schenk wrote: > > I've committed changes to the QA area complete with the "index" > capability > > of the new test case area. I'll be working on additional changes to the > QA > > area over the next few days before a general announcement to QA. > > > > NOTE: the staging web site -- http://ooo-site.staging.apache.org/ -- > allows > > for +Indexes automatically so displays can be misleading in that > > environment. Our default setup for -- http://www.openoffice.org/ -- does > > not. > > > > We should probably request that infra setup both these servers the same. > > > > > Kay; > > Just tried to check out ooo-site repo in preparation for completing the > download of all the Impress test cases and ran into a problem. You have > a number of files that include an * in the filename. This is no-no on > windows and causes a corrupt working copy on Windows that can not be > used. Can you update the ooo-site repo and replace those 1/2 dozen or so > files with * in the names so that I can check out a new working copy? > Yes, I will do that. > > Also a process question. Why did you chose to put all the tests in a > single directory rather than breaking it down by application the way > they were on the testlink site? An oversight on my part, but as I got into this, I did see there was a LOT of overlap, with the former QA folks establishing categories for some very specific areas. We can probably restructure this new area just based on file names and move things around. I discovered on the original TestLink site that there were MANY fine-grained categorizations that we probably don't need. > The process engineer in me says that it > would be cleaner to do it by application so that a volunteer working on > Writer doesn't have to wade through tests that do not apply to them to > find the Writer specific ones. > I thought perhaps the file names themselves would suffice for determining categories. In any case, please feel free to organize this area further. I would think subareas for Wrtier, Calc, Impress, Database, Drawing would be enough -- or not. > > Regards > Keith > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- -- MzK "Less is MORE."
Re: [WEBSITE] QA area changes, and differences between staging and production
On 3/30/2018 3:15 PM, Kay Schenk wrote: > I've committed changes to the QA area complete with the "index" capability > of the new test case area. I'll be working on additional changes to the QA > area over the next few days before a general announcement to QA. > > NOTE: the staging web site -- http://ooo-site.staging.apache.org/ -- allows > for +Indexes automatically so displays can be misleading in that > environment. Our default setup for -- http://www.openoffice.org/ -- does > not. > > We should probably request that infra setup both these servers the same. > > Kay; Just tried to check out ooo-site repo in preparation for completing the download of all the Impress test cases and ran into a problem. You have a number of files that include an * in the filename. This is no-no on windows and causes a corrupt working copy on Windows that can not be used. Can you update the ooo-site repo and replace those 1/2 dozen or so files with * in the names so that I can check out a new working copy? Also a process question. Why did you chose to put all the tests in a single directory rather than breaking it down by application the way they were on the testlink site? The process engineer in me says that it would be cleaner to do it by application so that a volunteer working on Writer doesn't have to wade through tests that do not apply to them to find the Writer specific ones. Regards Keith - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Dummy text in Windows installer
On 31/03/2018 Marcus wrote: Am 30.03.2018 um 18:45 schrieb Matthias Seidel: My question is, what impact does it have on Pootle synchronization if I also delete the unused string from: /main/instsetoo_native/inc_openoffice/windows/msi_languages I've no clue what will happen with Pootle. Maybe Andrea has an idea? I don't think this will have a bigger impact than other changes that are already in trunk. We are still quite behind in the localization process for 4.2.0, not yet at a point where we have the full process under control. But this shouldn't block improvements. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org