Re: [Mantisbt-dev] Mantis to cvsweb integration andper-project resolution states?

[Cheng-Jih C. <cc...@ra...>]

Kenzaburo Ito wrote:
> 
> Hiya,
> 
> I'm not sure about the per project items that you mention but the cvs stuff
> is definitely doable.  It sorta depends on how complicated you want to make
> it.  I'm willing to take any form that you'd like since I don't think we
> have anything very advanced in place.
> 
> I see a scenario like this mostly: you specify a cvs tag like
> cvs://main/main.c:2.4 and it would be a converted to a hyperlink to that
> project's cvsweb url and go to directory main and open file main.c with
> version 2.4.  I don't know cvsweb or viewcvs very well but it looks like
> you could specify those on the URL line.
> 
> Your thoughts?  Would this method be sufficiently powerful to achieve what
> you need for CVS integration (so we could avoid the tables)?

I'm considering the new table or tables because it's possible that a
single bug may refer to several files for its resolution, and this sort
of relationship calls for a table to contain these references to the
version control system.

But, yes, basically, developers would enter a cvs tag, and it would show
up
as a hyperlink in the web interface to the repository.


> >Hi.
> >
> >We've started using Mantis to provide bug tracking to a team of developers
> >working at a client site.  It's working well so far, though they've requested
> >a few features.  Many of these features seem to be in the development roadmap,
> >so we can probably wait on them.
> >
> >A couple of things that were requested but don't seem to be in the roadmap are
> >per-project resolution states, priorities and workflow, and hooks into version
> >control.
> >
> >For the resolution states, priorities and workflow feature, we basically need
> >issue workflow to match up with our contracts' acceptance procedures and
> >terminology.  These are generally constant between contracts, so I suppose I
> >can perform site-customization, but it'd be nice to be able to change these
> >things on a project-by-project basis.
> >
> >The other thing missing is something that our current issues tracking system
> >doesn't do very well, but would be very nice to have: we'd like to be able
> >to link specific bugs to specific files and versions in our version control
> >system, basically as a reference to which file and which version fixed which
> >bug.  We're using CVS for version control, and have cvsweb running to provide
> >a browser interface to the repository.
> >
> >For hooking into CVS, I was thinking it'd be sufficient to include references
> >in a bug that point to URLs as presented by cvsweb, sort of analogous to how
> >uploaded files are handled.  This would require a new table to contain
> >bug-to-CVS references, along the lines of:
> >
> >  CREATE TABLE mantis_cvs_reference_table (
> >     id int(7) unsigned zerofill DEFAULT '0000000' NOT NULL auto_increment,
> >     bug_id int(7) unsigned zerofill DEFAULT '0000000' NOT NULL,
> >     cvs_file_name varchar(512),
> >     cvs_file_version varchar(64),
> >     PRIMARY KEY (id)
> >  );
> >
> >(Though a better way to do this would be to have a table that contains only
> >CVS references, and a many-to-many table to link bugs to CVS references.
> >That, however, may be more complicated than what's required.)
> >
> >The view_bug_page.php and view_bug_advanced_page.php can be easily modified
> >to present HREFs to cvsweb URLs that would bring up referenced files.  Of
> >course, some sort of entry screen would also be needed.
> >
> >I've done a little bit of work to put in CVS hooks in our installation of
> >0.16.1.  Would the Mantis project be interested in all of this?
> >
> >Oh, we currently use Tower Software's Razor Issues for bug tracking, a
> >commercial
> >product.  It's old, creaky, and obscure.  Mantis is generally an
> >improvement over
> >this system.
> >
> >Thanks!