<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.12-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Keeping Trac of Bugzilla</title>
	<link>http://www.lshift.net/blog/2006/11/27/keeping-trac-of-bugzilla</link>
	<description>What happens at LShift</description>
	<pubDate>Tue, 06 Jan 2009 21:23:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.12-alpha</generator>

	<item>
		<title>by: Felipe Pereira</title>
		<link>http://www.lshift.net/blog/2006/11/27/keeping-trac-of-bugzilla#comment-53591</link>
		<pubDate>Sat, 05 May 2007 21:12:24 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2006/11/27/keeping-trac-of-bugzilla#comment-53591</guid>
					<description>&lt;p&gt;In fact, I think I finally found it...
http://trac.edgewall.org/wiki/TracFaq#we-re-already-using-bugzilla-can-i-disable-tickets&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>In fact, I think I finally found it&#8230;<br />
http://trac.edgewall.org/wiki/TracFaq#we-re-already-using-bugzilla-can-i-disable-tickets</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Felipe Pereira</title>
		<link>http://www.lshift.net/blog/2006/11/27/keeping-trac-of-bugzilla#comment-53589</link>
		<pubDate>Sat, 05 May 2007 21:02:23 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2006/11/27/keeping-trac-of-bugzilla#comment-53589</guid>
					<description>&lt;p&gt;I'd like to replace Trac tickets links #nnnn with my Bugzilla's bugs links. Is that possible with your tool?
thanks in advance,
Felipe&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to replace Trac tickets links #nnnn with my Bugzilla&#8217;s bugs links. Is that possible with your tool?<br />
thanks in advance,<br />
Felipe</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: tom</title>
		<link>http://www.lshift.net/blog/2006/11/27/keeping-trac-of-bugzilla#comment-18700</link>
		<pubDate>Mon, 27 Nov 2006 21:43:00 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2006/11/27/keeping-trac-of-bugzilla#comment-18700</guid>
					<description>&lt;p&gt;@Igor,&lt;/p&gt;

&lt;p&gt;Trac not being to properly support the management of multiple projects is probably the biggest problem preventing us from adopting  it wholesale (we're only using it on one project right now - guess which :-]).&lt;/p&gt;

&lt;p&gt;Apart from the work the Trac team is putting into converting Trac to a multi-project scheme (and I understand that this work is not expected to be completed before v2.0 is out of the door in a year or so), there are still a few tricks we could consider using:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Managed deployment - use a common codebase and create tools for automating the creation and management of new projects.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;InterTrac and InterWiki - two new plugins which are slated for inclusion in the core Trac soon, designed to make it easier to connect, on the content level, one Trac instance to the other.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Managed authentication and user mangaement (using LDAP, for example).&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One of the main problems is that until Trac learns how to use a database server (like MySQL or Postgres, rather than the embedded database SQLIte) it will always be impossible to harvest data from multiple projects, and that's something we tend to do quite a lot (and I believe many organizations that run more than one project do).&lt;/p&gt;

&lt;p&gt;Still, I'm hopeful - watch this space!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Igor,</p>
<p>Trac not being to properly support the management of multiple projects is probably the biggest problem preventing us from adopting  it wholesale (we&#8217;re only using it on one project right now - guess which :-]).</p>
<p>Apart from the work the Trac team is putting into converting Trac to a multi-project scheme (and I understand that this work is not expected to be completed before v2.0 is out of the door in a year or so), there are still a few tricks we could consider using:</p>
<ol>
<li>
<p>Managed deployment - use a common codebase and create tools for automating the creation and management of new projects.</p>
</li>
<li>
<p>InterTrac and InterWiki - two new plugins which are slated for inclusion in the core Trac soon, designed to make it easier to connect, on the content level, one Trac instance to the other.</p>
</li>
<li>
<p>Managed authentication and user mangaement (using LDAP, for example).</p>
</li>
</ol>
<p>One of the main problems is that until Trac learns how to use a database server (like MySQL or Postgres, rather than the embedded database SQLIte) it will always be impossible to harvest data from multiple projects, and that&#8217;s something we tend to do quite a lot (and I believe many organizations that run more than one project do).</p>
<p>Still, I&#8217;m hopeful - watch this space!</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Igor Clark</title>
		<link>http://www.lshift.net/blog/2006/11/27/keeping-trac-of-bugzilla#comment-18698</link>
		<pubDate>Mon, 27 Nov 2006 21:24:54 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2006/11/27/keeping-trac-of-bugzilla#comment-18698</guid>
					<description>&lt;p&gt;Interesting stuff. What's your take on Trac and multiple projects within one repository, or has this not come up for you?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Interesting stuff. What&#8217;s your take on Trac and multiple projects within one repository, or has this not come up for you?</p>
]]></content:encoded>
				</item>
</channel>
</rss>
