Similarily, storing bugs and
issues information could be stored in SVN repository, all in human
readable
text format. Yes, this takes a lot of time. Am I talking too
ideally?
:)
That's an interesting point. Issue tracking is another artifact
that is
not stored in SVN. Would it be useful
2005/12/20, Ross Gardler <[EMAIL PROTECTED]>:
> > I always have imagined a web-based wiki application which stores its
> data in
> > a certain directory in SVN repository. Perhaps, we could create this
> kind
> > of backend extension for our existing CMS.
>
> The problem is that we are unlikely t
Trustin Lee wrote:
2005/12/20, David Crossley <[EMAIL PROTECTED]>:
...
The current operating principle is that we store all
source content in the official revision control system.
Some people have said that that is a dictate.
That includes everything: code, configuration files,
source conten
On 20 Dec 2005, at 04:10, David Crossley wrote:
With the advent of new documentation management tools
(e.g. Lenya, JackRabbit, Daisy) and their potential
use by ASF projects for their project documentation,
we are seeing questions about how to enable the
storage of the sources for documentation.
Hello David,
2005/12/20, David Crossley <[EMAIL PROTECTED]>:
>
> This is a topic that i often hear, not only at new projects.
> People are not sure what needs to be stored in svn and why.
>
> A while ago, Noel raised the issue on the infra@ list. [1]
> Unfortunately not much follow-up. So i wonder
