On Thu, 10 Aug 2006 09:15:14 +0200, MJ Ray <[EMAIL PROTECTED]> wrote:
"Jonas Karlsson" <[EMAIL PROTECTED]>
keeping our software repositories. The discussion has been up before,
which software to use for this. Afaic there's only one alternative for
SCM: SVN. There is probably those that think different and please speak
up
if so.
(Afaic?)
Please, don't require SVN. It adds considerable size over CVS without
solving the essential 'single point of failure' problem. I thought the
plan was to move to Git, which is young, but does solve that problem.
Some of the other distributed SCMs are also good.
I don't see the problem with centralized SCM and I actually like that
approach.
Anyhow, if distributed SCM is wanted I can see Git and Darcs as
alternatives, but are we looking for a distributed SCM? Why is that better
(besides of removing single point of failure, which is highly unlikely to
happen on a good server).
Either way, generating tarballs and diffs are vital. At Savannah, one
can do this from the web interface, and it's a function worth keeping.
I don't know what you mean about tarballs, but there's possibilities to
create diffs with SVN if one use ViewVC.
Look at
http://karlsson.sytes.net/viewsvn/gobolinux/tools/Compile/bin/Compile?r1=1&r2=2&diff_format=u
For bugtracking I see two alternatives: Mantis or Trac. [...]
RT would be the other big one IMO, but I've seen lots of groups struggle
to configure it.
Yes, that's why I didn't consider that. I've read up on bugtrackers and
the general idea is that one should use Mantis or Trac, therefore I went
for those.
--
/Jonas
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
