[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Tickets - my 2 cents

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: Fri, 20 Jun 2008 12:10:13 +0200

On 6/20/08, Florian Seydoux <florianseydoux_at_gmail.com> wrote:
> David Weintraub wrote:
> > [...]
> > This adds an amazing bit of power. In most defect tracking/source
> > control integrations, almost all queries must be handled via the
> > defect tracking system. For example, if I want to know what files were
> > changed by particular defects, I query the defect tracking system. If
> > you had Perforce and integrated the job control system into the defect
> > tracking system, almost all of your queries could be done directly
> > from the source control system. You could generate release notes
> > between two Perforce change sets and include all defects that were
> > fixed, how they were fixed, and when they were fixed.
> >
> well, with subversion, usually, you create a branche to fix a bug, and then,
> all commits to this branch have something to do with the bug.
> (you can retrive them very easily, import the changes (almost) where you
> want, etc.)
> In addition, the notion of bug (managed or not by a third party tools)
> imply that you specify, with a commit, some information (identification)
> about the related
> bug. This can be 'commit in a specific branch' (dedicated to the bug), but
> more frequently,
> you (also) give such identification through the commit log (like: BUG-1234)
> With such convention, looking for every commits having "BUG-1234") in their
> log message is easy.
> > [...] Of course, the answer whether Subversion has a ticketing system is
> > still "no", but it might be something interesting to consider in
> > future revisions of Subversion.

No, I think you're wrong there: we're focussed on version control.
What you expect from your version control system is stability and
correctness to protect your assets. Every line of code we add outside
of the scope of version control, the goals of stability and
correctness are harder to achieve (after all every line adds

So, talking from the historic point of view of the Subversion
developers, we're very strict with feature creep: features which do
not immediately support the core task of Subversion. It's unlikely
that Subversion will ever grow a ticketing system. If you need
additional (server side) hooks however to support integration with
your bugtracker / ticketing system, that's something we can talk

The solution of hooks is by far the most flexible anyway: some want to
use Trac, others Jira or Bugzilla. Through the use of hook we're able
to handle all of them, without specifying preference.

> hum... personnaly, I will be really disappointed if subversion will "offer"
> such kind of "feature"
> (deeply integrated, of course; having a "package" subversion+trac (for
> example) is perfectly acceptable)
> - my two cents -




To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-20 12:11:23 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.