[svk-devel] Mercurial (and NOT svk) chosen as Distributed SCM for OpenSolaris... Do we "Know" the reasons for rejection?

[F. Javier Jarava]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all!

I guess this is something some of you migh have seen already, but I though
it might be a good idea to shake it a bit.

It seems that the OpenSolaris project (http://www.opensolaris.org/os/) has
been searching for a distributed SCM tool to use in their work with the
community.
The reason for this: http://www.opensolaris.org/os/community/tools/scm/


As such, the feature set they were looking for was quite stingent and well
documented:
http://www.opensolaris.org/os/community/tools/scm/dscmreqdoc/

The tools they evaluated:
http://www.opensolaris.org/os/community/tools/dscmdownload/
As you can see, SVK is in the list of the tools that they had a look at.
But then, there were only three tools that made the cut: Mercurial, Git and
Bazaar

The chosen tool was Mercurial:
http://www.selenic.com/pipermail/mercurial/2006-April/007531.html

The thing is, I've been trying to find the reasons they had for rejecting
svk, because I believe the objections they found would be usefult to know.
Anybody has any leads on this?

Apart from that, I am (anxiously) waiting for the next svk :)

Thanks a lot for a great product to all of you who make it possible.


	Best regards,

		Javier Jarava
		jjarava at secuware.com

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.0.6 (Build 6060)

iQA/AwUBRRA9gGW7adqbADg+EQLVIwCdFjCkrF43GteZR4/SeGf9dsGxS24AoOX6
dhBXjZzHY/wr4f/rZvHqG1yk
=J4V4
-----END PGP SIGNATURE-----