Veracity distributed version control discussion ()

Slavo Furman | 23 Feb 2011 10:35

how can I be useful as an early veracity user?

Hello!

Question 1: Suppose I successfully built 64bit nightly build of
Veracity on Windows. Now I ran tests suite as described at the end of
build doc on your page. And few tests, say 2 to 4 of 238 failed. Do
you like to hear about this? Should I write about this to the list? Or
post my tests logs to somewhere/someone? Or I should to try figure
this out and just when I find something interesting about that
failure, just then write? Or do not write about these test failures
from nightly builds at all? What is most useful to you (as for
veracity devs/testers)?

Question 2: Suppose I successfully built 64bit nightly build of
Veracity on Windows. Now I ran tests suite, few tests, say 2 to 4 of
238 failed, but I decided to try given build of Veracity anyway. Now,
what would be most useful to you (as for veracity devs)? So Should I
just start use it (locally?) as source control solution for my hobby
project and while I do this I trying to learn-and-try various Veracity
features, and when I run to some error/difficulties with this - then I
should write about this to this list? Would you like me to try some
specific features at this moment of development? Or at contrary are
there some features (maybe not sufficiently stable) that I shouldn't
try yet? Are you like me to try veracity on some specific
configuration (which would be interesting for you) - I\m going to try
64bit windows build on win7 sp1, but I can setup VM and try it for
example as 32bit windows build on WinXP SP3,  or on Win2008R2.

Question 3: I have some experience with Git and Mercurial (limited) as
an user. It is a good idea to try use in similar way Veracity as I
used to use git/mercurial? Or there are things/features that I should

(Continue reading)

headers

Paul Roub | 23 Feb 2011 13:52

how can I be useful as an early veracity user?


> Question 1: Suppose I successfully built 64bit nightly build of
> Veracity on Windows. Now I ran tests suite as described at the end of
> build doc on your page. And few tests, say 2 to 4 of 238 failed. Do
> you like to hear about this? Should I write about this to the list? Or
> post my tests logs to somewhere/someone? Or I should to try figure
> this out and just when I find something interesting about that
> failure, just then write? Or do not write about these test failures
> from nightly builds at all? What is most useful to you (as for
> veracity devs/testers)?
>
We're *very* happy to hear about your failures (and successes) running 
and testing Veracity on any platform.  The feedback we've gotten from 
you so far has been very much appreciated.  This mailing list is, for 
the moment, our favorite place for this kind of feedback - whenever 
these issues are mentioned and addressed in public, everyone benefits.

> just start use it (locally?) as source control solution for my hobby
> project and while I do this I trying to learn-and-try various Veracity
> features, and when I run to some error/difficulties with this - then I
> should write about this to this list? Would you like me to try some
> specific features at this moment of development? Or at contrary are
> there some features (maybe not sufficiently stable) that I shouldn't
> try yet? Are you like me to try veracity on some specific
> configuration (which would be interesting for you) - I\m going to try
> 64bit windows build on win7 sp1, but I can setup VM and try it for
> example as 32bit windows build on WinXP SP3,  or on Win2008R2.
>
I can't think of specific features we *wouldn't* like you to test, at 
this stage - they're all largely untried beyond our team.  We'll still

(Continue reading)

headers

Michael Maddox | 23 Feb 2011 10:50

how can I be useful as an early veracity user?

I wrote a blog post on some of the differences I've found between
Veracity and Mercurial:

http://www.capprime.com/software_development_weblog/2011/01/20/SourceGearVeracityMercurialLookupChart.aspx

You can certainly help me flush out that chart.  Veracity is much more
similar to Mercurial than to git in my experience, although I have
called out a couple places where Veracity is more like git (for
example the default branch name is "master").

One thing I did was tried to go through Joel Spolsky's Hg Init
tutorial (http://www.hginit.com/) using Veracity and I think I
captured most of the items where the syntax was different in my blog
post, but if you notice anything that is wrong or missing, I'd love to
hear about it.

-Michael Maddox
http://www.capprime.com/About.htm

On Wed, Feb 23, 2011 at 9:35 AM, Slavo Furman <slavof@...> wrote:
> Hello!
>
> Question 1: Suppose I successfully built 64bit nightly build of
> Veracity on Windows. Now I ran tests suite as described at the end of
> build doc on your page. And few tests, say 2 to 4 of 238 failed. Do
> you like to hear about this? Should I write about this to the list? Or
> post my tests logs to somewhere/someone? Or I should to try figure
> this out and just when I find something interesting about that
> failure, just then write? Or do not write about these test failures
> from nightly builds at all? What is most useful to you (as for

(Continue reading)

headers

Ian Olsen | 23 Feb 2011 18:14

how can I be useful as an early veracity user?

This is cool, Michael.

I'm not sure why my Google alert for SourceGear Veracity didn't turn it 
up. :)

On 2/23/2011 9:49 AM, Michael Maddox wrote:
> I wrote a blog post on some of the differences I've found between
> Veracity and Mercurial:
>
> http://www.capprime.com/software_development_weblog/2011/01/20/SourceGearVeracityMercurialLookupChart.aspx