On Wed, Apr 05, 2006 at 05:16:25PM +0200, Niels Nes wrote:
MonetDB developers
Seems switching to another 'sourceforge' like service isn't an option. So we should try to get the best out of sourceforge. Reading their remarks and some of the subversion documentation, it seems a good idea to move to subversion. Does anybody have objections ?
Though I will not actually object, I am a bit sceptical about this.
-- Do we actually *know* SVN (on SourceForge) is any better than CVS?
"Reading their remarks and some documentation, it seems a good idea to move to subversion" does not actually convince me. CVS per se is not unreliable at all. Rather, we have been disappointed by the services provided by *SourceForge* in the recent past. That would still be the case if we switched to SVN. Your so right and before switching we plan to try out the conversion and svn here. If we find out that svn doesn't work or gives no improvement we will report that afcouse.
-- Do we really need a replacement for SourceForge CVS?
I guess the current urge to switch to something else is mainly due to the recent outage of SourceForge CVS. From my side, this is the only *major* CVS outage of SourceForge I can remember. For sure there have been issues every now and then, but that did not keep us from making significant progress in our development. And from what we heard from Fabian, SourceForge's services aren't that bad, compared to others. We allready thought of switching before Sourceforge offered the server. So its definetely not because of the recent long outage. This outage just made us thing about it again. The main improvement we are seeking is during the freeze periode, then checkouts on the release branch (and in general on the stable branch) are very slow. So if that is improved by svn we would be happy.
-- What would be the consequences when switching to SVN?
Personally, I don't have any experiences with SVN, so I'd have to learn something new. (In fact, I'd even have to install the software first, but both is not an actual problem :-).) What wonders me, though, is what impact the shift would have for, e.g., the TestWeb, Stefan's automated branch propagation scripts, etc. If it takes work on that side, my opinion is we'd better stay with CVS.
In short: I'm sceptical about switching to SVN, just because we have been annoyed by the recent CVS outage on SourceForge. Agreed we need more testing to prove its a good replacement. On the learning front most commands you know about CVS are the same in svn, but also there are some important differences. Stefan allready told me that any changes to
On Thu, Apr 06, 2006 at 09:40:29AM +0200, Jens Teubner wrote: the testweb will be small, ie some search and replace would do the trick. Niels
Jens
-- Jens Teubner Technische Universitaet Muenchen, Department of Informatics D-85748 Garching, Germany Tel: +49 89 289-17259 Fax: +49 89 289-17263
In theory, practice and theory are the same, but in practice they are different. -- Larry McVoy
------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes@cwi.nl