Re: Snapshot links at Cocoon website
On Tuesday, March 11, 2003, at 12:31 PM, Diana Shannon wrote: On Tuesday, March 11, 2003, at 05:32 AM, Pier Fumagalli wrote: I suggest linking to http://xml.apache.org/cocoon/mirror.cgi#nightly but I guess that's your intention ;-) Yes, but at that point we'll have to re-build the site once again... In the future, I think it's better if more committers would share the burden of updating the live site cvs every now and then, particularly those with greater bandwidth connections. In the hopes that this will happen, I'll post detailed instructions on how this can be done on wiki. (I've posted email instructions on two separate occasions in the past which I will now fine tune.) Hi Diana, Thanks for the effort you are making. It would be great to have some documentation on this stuff ... we ALL ought to be able to do it! regards Jeremy
Re: Snapshot links at Cocoon website
Diana Shannon wrote: 2. Updating the live site repository is time consuming, at least for me, on a slow dial-up connection (I live in a rural area of the US with no broadband option). The api docs directory is the time killer here. I spent eight hours, one night, simply performing a cvs update followed by a cvs commit. The most recent update wasn't so bad. The commit/update took only 2.5 hours. If you know things take time, you can nohup your processes, this way they keep on running after logout. Another very nice tool is "screen". It gives you virtual terminals inside your terminal emulator. In addition, you can detach it and attach to it at will. Your commands continue to run and their output is still on your screen when you re-attach. Never do admin jobs without it ;-) Chris.
Re: Snapshot links at Cocoon website
"Andrew Savory" <[EMAIL PROTECTED]> wrote: > On Tue, 11 Mar 2003, Diana Shannon wrote: > >> 1. Many, many committers weren't updating release and head branches with >> their doc updates. It took time to scrutinize differences in the >> branches, to make sure all relevant docs were in the release branch, >> which is what is used to generate the web site. > > Hrm. Did we ever reach a consensus on splitting docs out into a separate > CVS module? I still think it would be a _really_ good idea, as it makes no > sense as far as I can tell to maintain two sets of documentation (it's > hard enough getting people to contribute to it as it is, let's not place > more barriers in the way!). It sounds allright for me... > One more question: is there not a machine where we could run the site > "live" with Cocoon? Nagoya... But I want to upgrade it to Solaris 9 and VXFS first... And I'm waiting for Sun's licenses to come in... Pier
Re: Snapshot links at Cocoon website
On Tue, 11 Mar 2003, Diana Shannon wrote: > 1. Many, many committers weren't updating release and head branches with > their doc updates. It took time to scrutinize differences in the > branches, to make sure all relevant docs were in the release branch, > which is what is used to generate the web site. Hrm. Did we ever reach a consensus on splitting docs out into a separate CVS module? I still think it would be a _really_ good idea, as it makes no sense as far as I can tell to maintain two sets of documentation (it's hard enough getting people to contribute to it as it is, let's not place more barriers in the way!). One more question: is there not a machine where we could run the site "live" with Cocoon? Andrew. -- Andrew SavoryEmail: [EMAIL PROTECTED] Managing Director Tel: +44 (0)870 741 6658 Luminas Internet Applications Fax: +44 (0)700 598 1135 This is not an official statement or order.Web:www.luminas.co.uk
Re: Snapshot links at Cocoon website
On Tue, Mar 11, 2003 at 07:31:10AM -0500, Diana Shannon wrote: > 3. I was really excited about Forrest transition, thinking the > automation would save me all of the above time which I could devote to > docs content. Unfortunately: > - only a few committers participated in the trial run, so it seemed to > me, interest/support is not that great. > - Forresters seemed to suggest, and I could be wrong, that the live site > cvs update would **still** be required even with Forrest. Thus, I failed > to see how the transition would make my volunteer committer life any > more liberated, since this time killing step was still necessary. Last time this came up, I don't think the Forrestbot was fully operational. For many websites (xml-site, forrest, fop, avalon), the update/commit process is now automated (still human-triggered though). API docs are (IMHO) outside Forrest's concern. I think they should be updated separately to the main site -- Javadocs are *big* and committing them all for trivial updates will quickly full up icarus disk space. --Jeff > > Diana >
Re: Snapshot links at Cocoon website
On Tuesday, March 11, 2003, at 05:32 AM, Pier Fumagalli wrote: I suggest linking to http://xml.apache.org/cocoon/mirror.cgi#nightly but I guess that's your intention ;-) Yes, but at that point we'll have to re-build the site once again... Ok, we shouldn't be so limited in rebuilding the site as often as necessary. Here's why it has been tedious and time consuming in the past, at least for me. 1. Many, many committers weren't updating release and head branches with their doc updates. It took time to scrutinize differences in the branches, to make sure all relevant docs were in the release branch, which is what is used to generate the web site. 2. Updating the live site repository is time consuming, at least for me, on a slow dial-up connection (I live in a rural area of the US with no broadband option). The api docs directory is the time killer here. I spent eight hours, one night, simply performing a cvs update followed by a cvs commit. The most recent update wasn't so bad. The commit/update took only 2.5 hours. 3. I was really excited about Forrest transition, thinking the automation would save me all of the above time which I could devote to docs content. Unfortunately: - only a few committers participated in the trial run, so it seemed to me, interest/support is not that great. - Forresters seemed to suggest, and I could be wrong, that the live site cvs update would **still** be required even with Forrest. Thus, I failed to see how the transition would make my volunteer committer life any more liberated, since this time killing step was still necessary. I'm happy to help with updating the site based on the revised cvs mirror links discussed in this thread. However, I can't do it until later this week. In the future, I think it's better if more committers would share the burden of updating the live site cvs every now and then, particularly those with greater bandwidth connections. In the hopes that this will happen, I'll post detailed instructions on how this can be done on wiki. (I've posted email instructions on two separate occasions in the past which I will now fine tune.) Diana
RE: Snapshot links at Cocoon website
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Ok, it's working here as well, but shouldn't the links go > to cocoon-2.1? Good question ... I would link to http://xml.apache.org/cocoon/mirror.cgi#nightly but this would need a rebuild of the complete site (as Pier pointed out). But maybe this update can be done directly at the webserver and the CVS is updated in the same way. Reinhard
RE: Snapshot links at Cocoon website
Ok, it's working here as well, but shouldn't the links go to cocoon-2.1? Carsten > -Original Message- > From: Reinhard Pötz [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 11, 2003 11:55 AM > To: [EMAIL PROTECTED] > Subject: RE: Snapshot links at Cocoon website > > > > That is the only occurrence of the word "xml-cocoon2" on the > > server, all other problems are client-cache related... > > I checked it again and now the link is correct. Probably a proxy server > issue because client caching is turned off in all my browsers. > > Reinhard >
RE: Snapshot links at Cocoon website
> That is the only occurrence of the word "xml-cocoon2" on the > server, all other problems are client-cache related... I checked it again and now the link is correct. Probably a proxy server issue because client caching is turned off in all my browsers. Reinhard
Re: Snapshot links at Cocoon website
On 11/3/03 7:32, "Reinhard Pötz" <[EMAIL PROTECTED]> wrote: >> From: Pier Fumagalli [mailto:[EMAIL PROTECTED] >> >> On 10/3/03 7:42, "Carsten Ziegeler" <[EMAIL PROTECTED]> wrote: >> >>> b) Let's get the nightly build working asap >> >> Carsten, are you talking about the nightly builds (GUMP) or >> the nightly CVS snapshots??? >> >> Because if the latter, I was just waiting for the CVS >> repository split to integrate their automatic checkout back >> into the snapshotting scripts already ran by "root" on >> cvs.apache.org... >> >> And I've done that (well, just now, but at least one less >> problem to worry >> about) >> >> http://cvs.apache.org/snapshots/cocoon-2.0/ >> http://cvs.apache.org/snapshots/cocoon-2.1/ >> >> I also patched the "download" (mirror) page to reflect the change... >> >> http://xml.apache.org/cocoon/mirror.cgi#nightly > > Currently the link "Dev Snapshots" leads to > http://xml.apache.org/from-cvs/xml-cocoon2/. Maybe that's the reason why > it can't be found by many people. No it doesn't... I just checked... It goes to the quasi-correct http://cvs.apache.org/from-cvs/cocoon-2.0... That's what I just did on the server: /www/xml.apache.org/cocoon # find . -type f | xargs grep 'xml-cocoon2' ./plan/catalog.html: http://marc.theaimsgroup.com/?l=xml-co coon-dev&m=100303902726035&w=2">cvs commit: xml-cocoon2 LISCENSE.resol ver /www/xml.apache.org/cocoon # That is the only occurrence of the word "xml-cocoon2" on the server, all other problems are client-cache related... > I suggest linking to http://xml.apache.org/cocoon/mirror.cgi#nightly but > I guess that's your intention ;-) Yes, but at that point we'll have to re-build the site once again... Pier
Snapshot links at Cocoon website
> From: Pier Fumagalli [mailto:[EMAIL PROTECTED] > > On 10/3/03 7:42, "Carsten Ziegeler" <[EMAIL PROTECTED]> wrote: > > > b) Let's get the nightly build working asap > > Carsten, are you talking about the nightly builds (GUMP) or > the nightly CVS snapshots??? > > Because if the latter, I was just waiting for the CVS > repository split to integrate their automatic checkout back > into the snapshotting scripts already ran by "root" on > cvs.apache.org... > > And I've done that (well, just now, but at least one less > problem to worry > about) > > http://cvs.apache.org/snapshots/cocoon-2.0/ > http://cvs.apache.org/snapshots/cocoon-2.1/ > > I also patched the "download" (mirror) page to reflect the change... > > http://xml.apache.org/cocoon/mirror.cgi#nightly Currently the link "Dev Snapshots" leads to http://xml.apache.org/from-cvs/xml-cocoon2/. Maybe that's the reason why it can't be found by many people. I suggest linking to http://xml.apache.org/cocoon/mirror.cgi#nightly but I guess that's your intention ;-) Regards, Reinhard
