“There is really no good argument I have seen on
why one
should stick with svn.”
Except for the cost of migration, which could be
considerable given that the OASIS IT infrastructure is in the process
of a
major overhaul. Sometimes the best is the enemy of the good – in the
current
circumstances, I really do think you would need to explain the specific
and
measurable advantages over the current system and/or the dangers of
staying
with same…
Cheers,
Peter
(Speaking as an ordinary OASIS participant and
not on behalf
of the Board)
Hi David,
There are *more* clients on *more* platforms for mercurial that are
*better*
than *any* clients on *any* platform for svn:
http://en.wikipedia.org/wiki/Mercurial#Related_software
As for tortoisesvn you should check out:
http://en.wikipedia.org/wiki/TortoiseHg
There is really no good argument I have seen on why one should stick
with svn.
Even inertia does not count since mercurial's ConvertExtension can
convert from
most legacy VCS including svn seamlessly while preserving *all* history
of *all*
branches.
http://mercurial.selenic.com/wiki/ConvertExtension
Try converting to mercurial. IMHO, you will be very glad you did.
On 04/09/2010 01:15 PM, David RR Webber (XML) wrote:
I must
confess svn is my go-to solution -
and I cannot live without tortoisesvn client for Windows - using it
daily.
Is there
a similar solution for Mercurial
or git VCS? If there's something better - I'm definitely interested in
looking into it! I'm familiar with some svn limitations.
You are
indeed correct that it had escaped
my attention that OASIS now has svn - and most definitely this is
something now
as a priority to facilitate specification work - so I will look into
this
soonest.
--------
Original Message --------
Subject: [oasis-member-discuss] Request for mercurial or git
distributed VCS
From: Farrukh Najmi <farrukh@wellfleetsoftware.com>
Date: Thu, April 08, 2010 6:35 pm
To: oasis-member-discuss@lists.oasis-open.org
Dear colleagues,
I was pleased to hear recently that OASIS is now offering svn as a
Version Control System (VCS).
This is a good thing and will benefit spec artifact management in a
more
open and collaborative manner.
The result will be better specs done faster and with all the
transparency that they deserve.
I have one big followup wish though...
svn was great several years back but today it is quite limiting a
choice
now that
distributed VCS such as Mercurial (aka hg) and git (used by the Linux
project) are mature and stable.
The benefits of mercurial or git are huge over svn. Here is a nice
article on mercurial that explains the benefits:
http://hginit.com/index.html
Not many TC projects even know that svn is available yet. So please
could OASIS consider changing to (or providing as an alternative)
mercurial or git VCS. I would be glad to help OASIS staff with any
mercurial related questions offline if that will improve the chances of
getting my wish.
Earlier OASIS granted me my wish to offer JIRA for issue tracking
(thank
you!). I hope that I will get lucky again and OASIS will offer
mercurial
or git very soon.
Note that I would consider the benefits of mercurial or git over svn to
out-weigh any benefits of tigher integration between JIRA and svn.
OASIS staff please feel free to contact me on or off this list if you
would like to discuss this suggestion in more detail. Thank you for
your
consideration.
--
Regards,
Farrukh
Web: http://www.wellfleetsoftware.com