On Mon, 24 Mar 2003, Paul Lussier wrote:
> I was just trying to determine exactly what sw the issue tracker was.
> I knew it wasn't bugzilla, and thought that maybe they were using
> other CollabNet sw like Scarab, but that doesn't seem to be the case
> either. I could find no mention on the svn site of what sw ran the
> issue tracker either (unless I just wasn't looking in the right place :)
It's bugzilla, but forked long ago and renamed "IssueZilla", or IZ. I
*thought* there was an XML interface to querying, but I don't think it's
been deployed to tigris.org.
> Which also let me to the question, at which point will
> CollabNet-based projects which have achieved the 'self-hosting' mile
> stone, begin using the other self-hosting sw on CollabNet?
> (e.g., when well svn use scarab and vice-versa?)
When we upgrade tigris.org to 2.5 (sometime after the end of this month,
when 2.5.0 is completed, and as we can find spare time to do the upgrade
and data migration) then Scarab will be "production-ready" in the
application, which means we'd be able to use it, and migrate old issues
out of IZ to it. Subversion will be "early-access", which means we may
enable it per project - I'd imagine we'd still want to use the self-hosted
one at svn.collab.net for awhile, until a release of Sourcecast where SVN
is production-ready.
Unfortunately I can't give you a date; I can say that the people
who'd do the upgrade are the same who feel the pain from not having these
tools.
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 24 19:30:46 2003