Re: [ECOS] Looking in a future: VCS for eCos 3.0

[Jonathan Larmour <jifl@eCosCentric.com>]

Sergei Gavrikov wrote:
> Hello
> 
> It's possible it is an off-topic, but, looking in the nearest future of
> eCos project http://sourceware.org/ml/ecos-discuss/2008-07/msg00057.html
> I did think, It's possible, it is a good moment to change VCS (version
> control system) for eCos development? A couple of years it was/is CVS.
> The CVS has a well know limitations, and today, most of the developers
> select Distributed VCS. The famous are bk, git, hg. ... I do not want
> to fire the VCS flame here, but, if in the "eCos 3.0 planning" said

A switch of VCS is probably something to tackle very soon after eCos 3.0
rather than before. I agree that it's time to move forward from CVS.

I've had a look at Bazaar and would need a bit of convincing personally, at
the least at this stage of its development.  I found this an interesting
read:
http://sayspy.blogspot.com/2006/11/bazaar-vs-mercurial-unscientific.html
(including the comments). I'm still more inclined towards Mercurial,
although SVN is an obvious possibility just really due to its more
widespread use and slightly better client support (in addition both of
which are available on sourceware.org, but Bazaar isn't). But I'd really
really prefer to have something distributed.

When the time comes, we can see what it looks like then. The decision isn't
just mine of course.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss