Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ap-cocoon-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@cocoon.apache.org
From: BURGHARD =?ISO-8859-15?Q?=C9ric?= <eric.burghard@systheo.com>
Subject: Re: Creating a Bugzilla RSS feed using Cocoon
Date: Wed, 14 Sep 2005 11:12:48 +0200
Lines: 66
Message-ID: <dg8pd7$n4u$1@sea.gmane.org>
References: <F879B1E9-47A8-42B1-9E9B-1F31BD605126@betaversion.org>
 <43269DD0.8090703@apache.org> <20050913101919.GA948@vision.anyware>
 <0FBF3210-7C12-4DD0-93F9-E9F4B9A1B897@betaversion.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8Bit
User-Agent: KNode/0.9.2
Sender: news <news@sea.gmane.org>

Hi,

I tryed jira when i was looking for a bug-tracking system for my project,
and finally prefered bugzilla for its simplicity (well my project is not as
big as cocoon), even if i found it quite ugly compared to jira.

Then i found Trac[1], i think it could be valuable for cocoon if you look
for a bugzilla replacement candidat. You should definitively try a look at
it. It's extremly simple and usefull.

It can replace your wiki, your subversion browser and bugzilla. It provide
very clean bugs reports (fully customisable), milestones status with
charts[2]. Perhaps the most usefull feature is that you can link every
information from all the parts.

All texts can be writen with a wiki syntax[3]: commit message, wiki pages,
milestone descriptions, ticket description/comment. Syntax coloring is
available for your code snippets (js,sql,java,c,...).

The linking feature is perhaps the most usefull. I can wrote in every part
of Trac, something like

 * 'see #314' to provide a link to bug 314 description
 * 'see [312]' for link to repository revision 312
 * 'see {4}' for a link to a custom bug report (n�4)
 * 'milestone:brouzouf' for a link to the milestone description. Milestone
view provide a clean charts component by component to see on which part you
should concentrate.
 * 'see CFormsBinding' for a link to a wiki page
 * 'see source:cocoon/trunk/build.xml' for a link to a particular source in
the repository

After that, looking for every aspect of your developpement (roadmap,
tickets, sources, specs) is just a matter of clics.

One problem with bugzilla or other tracking systems is that you should
manually synchronise bugs and revisions. With Trac, some hook scripts are
provided for subversion which interpret commit messages like

"blabla. fixe #56, ref #314 ad #254"

and automaticly close ticket #56 and add the commit message to ticket #314
and #254 without the need to go into the bugtracking system.

Tickets[4] report are fully customisable. RSS feeds[5] are provided for
every aspect of Trac (tikets, reports, wiki changes, milestone changes),
separated or mixed. The subversion browser[6] is better that WebSVN.

Finally, it's ligth, really easy to install and setup, and easy to modify
(python). There is a bunch of wiki macros[7] that let you add TOC,
FootNotes, SideMenus, Tags, to your pages (plugins).

The migration from bugzilla is painless (at least for 2.16, but i submit a
patch for bugzilla 2.18), and you can import all your MoinMoinWiki pages.

My 0.2�

Regards

[1] http://projects.edgewall.com/trac/
[2] http://projects.edgewall.com/trac/milestone/0.9
[3] http://projects.edgewall.com/trac/wiki/TracWiki
[4] http://projects.edgewall.com/trac/report
[5] http://projects.edgewall.com/trac/wiki/TracRss
[6] http://projects.edgewall.com/trac/browser
[7] http://projects.edgewall.com/trac/wiki/MacroBazaar