I see that Scarab (scarab.tigris.org) is about to go 1.0 release real
soon now. Back in 2000-2001 when I first started following development
of Scarab and Subversion I got the impression that, just as SVN was the
"natural" successor, Scarab would be the "natural" successor to
Bugzilla. (Of course we now know about the split between Scarab
development and ProjectTracker as supported by CollabNet -- though I
wouldnt mind an update/refresher.)
Subversion has been doing amazingly well and getting great press (not to
mention the Jolt award - congrats guys, you deserve it). I think it
clearly has established itself as the successor to CVS and is or will
soon be the new "defacto" open-source version control tool.
The case is very different for open-source tracking tools, and I dont
see any evidence of Scarab establishing itself as the "new" defactor
standard (potentially succeeding Bugzilla). Im sure there are several
reasons for this:
* Version-control tools are generally in more widespread use than
tracking tools (I see plenty of shops with a VC tool and no tracker, not
so the other way around)
* The "defacto standard" tracking tools arent nearly as "de facto" as
CVS was for version control
* Im not aware of any "Change Tracking with Scarab" book (or its
equivalent) from O'Reilly or any other comparable publisher
So I have to wonder, what, if anything, are the front-runners for the
next-generation OSS "tracking" tools that will be the natural successor
for the likes of Bugzilla? (Too bad Jira isnt open-source, it would get
my vote)
And will/should there be any kind of model/framework for integrating
change-tracking with Subversion (which I fondly call "SubTraction" only
with partial tongue-in-cheek) in a way that supports some higher-level
abstractions for change-tracking the way that Subversion does for VC
over CVS? (E.g., the tracking equivalent of project-oriented branching,
directory versioning, global-revision-IDs, etc.)
What do folks feel are those higher-level-concepts for tracking tools?
would they be things like:
* support for task/activity-based development
* issue tracking across multiple releases/variants/codelines
* what else?
What do you think?
--
Brad Appleton <brad@bradapp.net> www.bradapp.net
Software CM Patterns (www.scmpatterns.com)
Effective Teamwork, Practical Integration
"And miles to go before I sleep" --Robert Frost
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 4 07:54:35 2005