Eddie, I checked in the fix for the link issue. However, I don't have a key to sign the documentation kits. Can you post these? Thanks.
I also tried to copy the new single changed page and associated PDF file into the /www/beehive.apache.org/docs/1.0.2 directory but was unable to because of permissions. It looks like the file is only writable by you. If you change the permissions, I can copy the new files into place. Thanks, Carlin On 1/15/07, Eddie O'Neil <[EMAIL PROTECTED]> wrote:
Carlin-- It's good that someone caught that. :) This would just follow the usual way of updating a release documentation kit, namely: #1) Commit an update to branches/v1.0.2/... that fixes the problem #2) Rebuild the documentation kit (see Ant targets in branches/v1.0.2/build.xml) #3) Update the live website hosted in /www/beehive.apache.org/docs/1.0.2 with the new documentation kit, single changed page, etc. I'll make sure that this is captured in a wiki page somewhere. Let me know if you have questions. Thanks! Eddie On 1/15/07, Carlin Rogers <[EMAIL PROTECTED]> wrote: > Eddie, > > I was wondering what the process was to update a release build > document (not the site documents) out on the beehive web site. > > Greg Mally caught an issue with the 1.0.2 installation document, > http://beehive.apache.org/docs/1.0.2/installation.html > > The document has the correct text in the link for the download, > release-1.0.2.cgi. However, the actual link that was generated from > the installation.xml for href="site:beehive-release/current" points to > release-1.0.cgi. > > The installation.html document in the distribution has the same issue > but it's probably best to at least fix the document out on the Web > site. > > I can take care of this if you'd like but just wanted to know the > process for doing something like this. > > Thanks, > Carlin >
