Hello!
I'm not a developer in this project. In fact, I'm not even a
member! However, that does not prevent me from beeing curious. :-)
I've been looking a long time for a good CVS replacement, something that
can handle module versioning as well as file versioning. They both serve a
big purpouse.
>From reading the "Design" docs I can tell SVN is pretty much on the right
track.
Reading a lot didn't give me answers to some of my more interresting
questions:
1) Will there be support for issue tracking on atom level as well as
module level? I want to access the issue database the same way one would
access the file/source database; by simple commands. I dislike GUI's and
don't use them unless forced to.
For instance, a command like "svn issue list mymodule" could list all
issues within a certain module. Or simmilar. Will this be an option?
2) What kind of versionen system is used? I like the OSDN regular
(x.y.z-p) used, but I would also like it on atom level. That is, files and
directories NEED to have their own versions, but the project/module
version needs to be changed for every atom change as well. This is what
SVN does?
Looking forward to a ready beta release tarball!
/Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:44 2006