We're relying on the "xml-site" module to make the CVS updates, we'd have to
create our own "cocoon-site" CVS repository to be in line with all other
repositories...
But I'm thinking as well about the tediousness in rebuilding the site that
Diana outlined... It would be probably better to address all those issues
before moving to the new location...
The other possible option would be to have the cocoon site served by Cocoon
itself (I did setup a "trial" site on Nagoya some weeks ago), but probably
right now that would be aiming a little bit too high...
Pier
"Carsten Ziegeler" <[EMAIL PROTECTED]> wrote:
> Is updating the docs then the same procedure than before
> (updating from cvs)?
>
> Carsten
>
>> -----Original Message-----
>> From: Pier Fumagalli [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, March 11, 2003 1:30 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: are we ready to move to cocoon.apache.org?
>>
>>
>> "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote:
>>
>>> Things to do will be:
>>>
>>> 1) move the existing docs to the cocoon.apache.org virtualhost (please
>>> note that the copyright year on the web site is old!)
>>>
>>> 2) create permanent redirects from the old location to the new one (so
>>> that no links are broken)
>>>
>>> anything else?
>>
>> I would move it in a slightly different way, that will help us to be more
>> flexible wih the new/updated documentation for v2.1 comes out:
>>
>> 1) move /www/xml.apache.org/cocoon1/ to /www/cocoon.apache.org/v1.x/
>>
>> 2) setup permanent redirect from http://xml.apache.org/cocoon1/** to
>> http://cocoon.apache.org/v1.x/{1}
>>
>> 3) move /www/xml.apache.org/cocoon/ to /www/cocoon.apache.org/v2.0/
>>
>> 4) setup permanent redirect from http://xml.apache.org/cocoon/** to
>> http://cocoon.apache.org/v2.0/{1}
>>
>> 5) setup temporary redirect from http://cocoon.apache.org/ to
>> http://cocoon.apache.org/v2.0/ (this will be changed to redirect to
>> http://cocoon.apache.org/v2.1/ when we want to put live a new 2.1 based
>> website)
>> note that this redirect doesn't "redirect" the entire subtree
>> (no ** and
>> no {1} in this one).
>>
>> 6) move the mirror.cgi and mirror.html fies to /www/cocoon.apache.org/ and
>> keep them as generic as possible for all our downloads (1.x, 2.x, ...)
>>
>> This should not break any link right now, and at the same time, it will
>> allow us to grow beyond 2.0 (whilst keeping the old doccos on line and
>> without having to move them as we did with 1.x)...
>>
>> And it will only take a few minutes to set up... Let me know if I should
>> shoot for it...
>>
>> Pier
>>
>
>
>
