Re: storing particular release documentation in SVN in our project web-site pages

2008-07-28 Thread Marshall Schor
Thilo Goetz wrote: Adam Lally wrote: On Fri, Jul 25, 2008 at 10:07 AM, Thilo Goetz [EMAIL PROTECTED] wrote: So you're saying having the old documentation is marginally useful. Then I suggest we create an archive section where we put all the old stuff, distributions and documentation. Less

Re: storing particular release documentation in SVN in our project web-site pages

2008-07-25 Thread Thilo Goetz
Adam Lally wrote: On Thu, Jul 24, 2008 at 4:40 PM, Marshall Schor [EMAIL PROTECTED] wrote: The current situation is that we have in SVN copies of the docs (Javadocs, plus docbook docs in html and pdf format) for all releases (of UIMA). Well, that's not quite accurate - some of the previous

Re: storing particular release documentation in SVN in our project web-site pages

2008-07-25 Thread Tong Fin
Let's look at this from the user's perspective. Who of our users needs access to all the old documentation? +1 I agree. I only has a link and access to current document. If there is a significant number of people who would benefit from this, then I'm for it. If I need the old documents, I

Re: storing particular release documentation in SVN in our project web-site pages

2008-07-25 Thread Adam Lally
On Fri, Jul 25, 2008 at 3:09 AM, Thilo Goetz [EMAIL PROTECTED] wrote: Let's look at this from the user's perspective. Who of our users needs access to all the old documentation? If there is a significant number of people who would benefit from this, then I'm for it. Else, let's not put up

Re: storing particular release documentation in SVN in our project web-site pages

2008-07-25 Thread Thilo Goetz
Adam Lally wrote: On Fri, Jul 25, 2008 at 3:09 AM, Thilo Goetz [EMAIL PROTECTED] wrote: Let's look at this from the user's perspective. Who of our users needs access to all the old documentation? If there is a significant number of people who would benefit from this, then I'm for it. Else,

Re: storing particular release documentation in SVN in our project web-site pages

2008-07-25 Thread Adam Lally
On Fri, Jul 25, 2008 at 10:07 AM, Thilo Goetz [EMAIL PROTECTED] wrote: So you're saying having the old documentation is marginally useful. Then I suggest we create an archive section where we put all the old stuff, distributions and documentation. Less clutter, but it's still around.

Re: storing particular release documentation in SVN in our project web-site pages

2008-07-25 Thread Thilo Goetz
Adam Lally wrote: On Fri, Jul 25, 2008 at 10:07 AM, Thilo Goetz [EMAIL PROTECTED] wrote: So you're saying having the old documentation is marginally useful. Then I suggest we create an archive section where we put all the old stuff, distributions and documentation. Less clutter, but it's still

storing particular release documentation in SVN in our project web-site pages

2008-07-24 Thread Marshall Schor
Currently, our uima-website project stores a copy of each release's documentation. This can be quite large, mainly due to the Javadoc API storage which is around 20 MB. A previous discussion pointed out that this was probably not an issue for SVN, which was cited as being good for storing lots

Re: storing particular release documentation in SVN in our project web-site pages

2008-07-24 Thread Adam Lally
On Thu, Jul 24, 2008 at 4:40 PM, Marshall Schor [EMAIL PROTECTED] wrote: The current situation is that we have in SVN copies of the docs (Javadocs, plus docbook docs in html and pdf format) for all releases (of UIMA). Well, that's not quite accurate - some of the previous releases didn't have