Perforce has a built-in mechanism (which was originally meant to work
internally) for attaching 'jobs' to changelists (changesets.) It's
basically another data type artifact that is designed to hold specific
data, kind of like a global to-do list.
This basically acts as your interface into just about any generic bug
tracking tool you want to use. Instead of hooking perforce directly to
bug tracking through API calls (hacking, maybe) you can just sync your
bugs to the jobs list and attach them to changes willy-nilly. The code
to do the hooking is open source and is easy to adapt to tools that
don't already support it.
I guess it can be described as a built-in interface to bug tracking.
(instead of using your own meta-data/attributes, rolling your own
interfaces into it, etc.) The jobs/bugs are query-able with Perforce
tools in a standard way, thusly you can run triggers on them (to, for
example, prevent a checkin if bugs are not attached.)
If you're going to hook Perforce into a bug tracking tool, it's pretty
cool. If not, it's utterly useless ;).
-Matt
-----Original Message-----
From: kfogel@collab.net [mailto:kfogel@collab.net]
Sent: Tuesday, June 28, 2005 8:35 AM
To: Janulewicz, Matthew
Cc: users@subversion.tigris.org
Subject: Re: SVN / PERFORCE comparison
"Janulewicz, Matthew" <MJanulewicz@westernasset.com> writes:
> I admined Perforce for a few years and really loved it, and am just a
> casual Subversion experimenter. So, at the risk of alienating (more)
> people on the list, I'll give a few points (not already mentioned)
that
> are also nice about Perforce.
>
> * Okay, already mentioned, but SPEED. It's uber fast in everything it
> does.
> * 'Real' tags, if that's your thing.
> * Easier to hook into bug tracking with 'jobs' mechanism.
> * GUI support, cross platform (unified looking/acting, QT based,
Windows
> and *nix look identical.)
> * World class support.
> * Better/more granular permissions mechanism.
> * Good training/consultant network.
> * Many many plugins for many many IDE's etc.
>
> The 5th item up there might be important if you are not at a company
> that already embraces open source and isn't used to the support model.
> The authors and contributors to Subversion frequent this list and it's
> good, but they don't have all the time a paid support professional
will
> have for you, and Perforce blows away any support group I've ever had
to
> deal with. Problems are rare (but it is a Berkeley DB) but they do
crop
> up, and it's nice to be helped by someone that knows what they're
> talking about in 10 minutes, instead of waiting for a list response.
> (Note that Perforce has a very active mailing list, too.)
Note that there is paid support/consulting/training available for
Subversion, visit http://www.collab.net/subversion/ for more. The
network is probably not as big as Perforce's yet, but it's growing all
the time.
Can't argue with the other points. There are a lot of areas where we
can improve. I think the GUI support and plugins will happen
naturally over time (they're already happening). As for "SPEED", yes,
that's a question of coding -- it won't happen naturally, we actually
have to do something about it :-).
I don't know much about this 'jobs' mechanism, care to describe?
Thanks,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
**********************************************************************
E-mail sent through the Internet is not secure. Western Asset therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Western Asset therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 28 18:41:37 2005