Hi Kay, The deletion of the index.html is not published: https://cms.apache.org/ooo-site/publish?diff=1
Regards, Matthias Am 09.06.2018 um 19:20 schrieb Kay Schenk: > Keith, short update -- see below > > On Sat, Jun 9, 2018 at 9:31 AM, Kay Schenk <[email protected]> wrote: > >> On Fri, Jun 8, 2018 at 12:03 PM, Keith N. McKenna < >> [email protected]> wrote: >> >>> 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 < >>> [email protected]> >>>>>> 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: >>>>>>>>>>> <snip> >>>>>>>>> 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. >>> >> >> Typically, the sequence of events for changes to the web server is to: >> * commit your changes, >> * review on the staging server (ooo-site staging >> <http://ooo-site.staging.apache.org/>), >> * then publish to the production server if all is well. >> >> I use the "Easy Publish" facility from https://cms.apache.org/. >> Once you supply your ASF credentials, navigate to ooo-site, and just click >> "Publish ooo-site". >> >> For now, I deleted the old index.html. I will need to modify the script to >> accommodate directory structures rather just a list of files. So, hopefully >> by mid-week, we will have the Impress items "show up". Thank you again for >> all your work. >> > 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. > > > >> >> >>> 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." >> > >
smime.p7s
Description: S/MIME Cryptographic Signature
