« Return to Thread: CVS migration to SVN?
Re: CVS migration to SVN?
by KP Kirchdoerfer-2
::
Rate this Message:
Am Donnerstag, 12. März 2009 18:56:09 schrieb Mike Noyes:
> Everyone,
> I think we should migrate to SVN. SVN integrates with Track well, and:
>
> <moorman> 1. Availability will be better on other services; we
> have a more scalable and resilient infrastructure under them
> <moorman> 2. Performance will be substantially better for any
> ops that actually involve data compares or over the wire
> communication
> <moorman> 3. Non-developers behind a firewall won't need to talk
> to their admin about punching a hole for 2401 to get pserver
> access to your repo
Mike;
I do not see a real need to migrate.
The current cvs usage "just works" and I haven't heart complains from users
that there are any difficulties using cvs. Not to mention performance pb's
with the few checkouts a week.
Given that I'm the one, who has done most of the commits the last two years
and every tag since we started to use cvs seriously, I'd like to stick to
what I'm used to.
And keep in mind a few tools to make release rely on cvs, these has to
reworked, if we switch to svn.
kp
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
leaf-devel mailing list
leaf-devel@...
https://lists.sourceforge.net/lists/listinfo/leaf-devel
> Everyone,
> I think we should migrate to SVN. SVN integrates with Track well, and:
>
> <moorman> 1. Availability will be better on other services; we
> have a more scalable and resilient infrastructure under them
> <moorman> 2. Performance will be substantially better for any
> ops that actually involve data compares or over the wire
> communication
> <moorman> 3. Non-developers behind a firewall won't need to talk
> to their admin about punching a hole for 2401 to get pserver
> access to your repo
Mike;
I do not see a real need to migrate.
The current cvs usage "just works" and I haven't heart complains from users
that there are any difficulties using cvs. Not to mention performance pb's
with the few checkouts a week.
Given that I'm the one, who has done most of the commits the last two years
and every tag since we started to use cvs seriously, I'd like to stick to
what I'm used to.
And keep in mind a few tools to make release rely on cvs, these has to
reworked, if we switch to svn.
kp
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
leaf-devel mailing list
leaf-devel@...
https://lists.sourceforge.net/lists/listinfo/leaf-devel
« Return to Thread: CVS migration to SVN?
| Free embeddable forum powered by Nabble | Forum Help |
