[Xastir-dev] SourceForge upgrade

[Jason Godfrey]

Even though I've only sent in a few patches, I thought I would throw in my
.02.

At work we use SVN. I don't have any complaints about SVN. However, I and
several others have been using git on top of SVN. Git's cheap and easy
branching is wonderful. In my experience it's one of those things that you
don't realize how useful it is until you have it.

I have even been using git for xastir. I use the master brach to track the
CVS repository, and have a branch for my IPv6 work (which I largely gave up
on since John was working on it) and another branch to do my shapefile
speedup experiments. It helps keep different project separate.

That being said, git does have a bit of a learning curve, but there is
helpful documentation online.

In short, I'm sure my vote counts for very little, but I'd vote for git.

- Jason



On Sun, Sep 16, 2012 at 11:51 AM, Tom Russo <russo at bogodyn.org> wrote:

> On Sun, Sep 16, 2012 at 09:30:28AM -0700, we recorded a bogon-computron
> collision of the <curt.we7u at gmail.com> flavor, containing:
> >
> > Git allows working offline, named changesets, sending patches between
> developers and merging, then deciding which to push out later.  It's also
> the one used by the Linux kernel developers since the BitKeeper agreement
> (commercial product) went south.
>
> A counter point here.
>
> These days, Xastir is not undergoing vibrant, constant development.  We
> have
> never used branching in the Xastir repository --- even experimental code
> has
> routinely been done on the single trunk.  CVS does support branching (my
> work
> project uses branching of CVS routinely and effectively), but it has never
> been used on this project.  So the fact that Git makes branching easier
> doesn't
> really mean too much.
>
> These days, most of the development is minor bug fixes.  The last real
> major
> feature addition was OSM maps, and that was two years ago.  That means
> that the
> lion's share of activity with the repository is people doing "cvs update"
> to get
> these minor bug fixes, since we've had no release in over two years.  Most
> of those are anonymous CVS grabs, not read/write developer access.
>
> As great as Git may be for large projects (it's in use by a major,
> multi-million-dollar-per-year library project where I work), I think it is
> severe overkill for Xastir.  In my experience, projects that have moved to
> Git
> are much more of a pain to deal with from the point of view of casual
> checkouts (which most of our CVS users are doing).  Seems that just to get
> a
> basic checkout requires that one pull down a whole clone of the repository
> at
> the first pass.
>
> If we were really vigorously persuing next-generation Xastir instead of
> just
> fantasizing about it every few years, I'd be game for making such a drastic
> switch.  But as it is right now, svn is more than adequate for Xastir's
> needs,
> and then only if Sourceforge forces us to do it.
>
> --
> Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
> Tijeras, NM  QRPL#1592 K2#398  SOC#236
> http://kevan.org/brain.cgi?DDTNM
> "And, isn't sanity really just a one-trick pony anyway? I mean all you get
> is
>  one trick, rational thinking, but when you're good and crazy, oooh, oooh,
>  oooh, the sky is the limit!"  --- The Tick
>
> _______________________________________________
> Xastir-dev mailing list
> Xastir-dev at lists.xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
>



-- 
"The problem with quotes on the Internet is that it is often difficult to
verify their authenticity." - *Abraham Lincoln*