On Wed, 07 Dec 2005 09:06:57 -0600, Kilian CAVALOTTI
[EMAIL PROTECTED] wrote:
On Wednesday 07 December 2005 14:06, Kilian CAVALOTTI wrote:
It's currently a per-trac-installation setting (as the format selection
lies in trac.ini), but it could/should/will be modified to become a
per-graph
On Wed, 07 Dec 2005 13:41:40 -0600, Kilian CAVALOTTI
[EMAIL PROTECTED] wrote:
Peter Kropf wrote:
One initial comment - it's better to avoid mixing tabs and spaces in
python code. A space is 1 character while a tab is user definable,
defaulting to 8. I've found viewing code with tabs
On Wed, 14 Dec 2005 10:02:58 -0600, Kilian CAVALOTTI
[EMAIL PROTECTED] wrote:
On Wednesday 14 December 2005 16:40, Russ Brown wrote:
The patch fails to apply for me too. :( This looks like really useful
functionality.
My bad...
Try the attached one.
I was very pleased to see the ability
(Apologies to moderators: original sent from the wrong email address)
Hello,
Has anybody had any luck with migrating an existing trac database from
sqlite to postgres? I've seen the tickets which call for a script for
doing the job, and
I'm just wondering if anybody has such a script that
On Tue, 20 Dec 2005 14:20:05 -0600, Jeff Weiss [EMAIL PROTECTED] wrote:
So the scenario is:
x projects. Same users. Each user has the same set of permissions
for each project.
As far as I know, there's nothing available in the stock version of
Trac to help automate that, other than apache
On Mon, 2 Jan 2006 02:03:36 +1100
Alec Thomas [EMAIL PROTECTED] wrote:
Hi,
I think a book is a good idea, particularly if it documents the Trac
API. The documentation is basically the code at the moment.
If you do go down this route I would suggest waiting for 1.0 before
starting.
On Tue, 03 Jan 2006 13:17:29 -0200
Alain [EMAIL PROTECTED] wrote:
Well, any interest in improving the Trac documentation is
appreciated, but I'm concerned that this would lead to a lot of
duplicated effort trying to maintain the online TracGuide as well
as a separate book format. Why
Help!
Our QA department want to stop using Trac for handling bug reports and
use Word documents instead handed around by email and stored on a
shared drive.
This is clearly utter lunacy, but they are convinced that this is a
better way to go.
It's difficult to extract their exact rationale, but
On Fri, 03 Feb 2006 15:59:33 +0100
Christian Boos [EMAIL PROTECTED] wrote:
Matthew Good wrote:
On Fri, 2006-02-03 at 08:33 -0600, Russ Brown wrote:
Help!
Our QA department want to stop using Trac for handling bug reports
and ...
I've seen a number of emails on this list and wiki
On Fri, 03 Feb 2006 17:05:26 +0100
Christian Boos [EMAIL PROTECTED] wrote:
Russ Brown wrote:
On Fri, 03 Feb 2006 15:59:33 +0100
Christian Boos [EMAIL PROTECTED] wrote:
...
Simple workflows can be configured directly in the trac.ini file.
It is possible to write more complex workflows
On Fri, 03 Feb 2006 17:05:26 +0100
Christian Boos [EMAIL PROTECTED] wrote:
Russ Brown wrote:
On Fri, 03 Feb 2006 15:59:33 +0100
Christian Boos [EMAIL PROTECTED] wrote:
...
Simple workflows can be configured directly in the trac.ini file.
It is possible to write more complex workflows
On Sat, 04 Feb 2006 12:26:56 +0100
Christian Boos [EMAIL PROTECTED] wrote:
Russ Brown wrote:
On Fri, 03 Feb 2006 17:05:26 +0100
Christian Boos [EMAIL PROTECTED] wrote:
Russ Brown wrote:
On Fri, 03 Feb 2006 15:59:33 +0100
Christian Boos [EMAIL PROTECTED] wrote:
...
Simple
Hi
We have been using trac for some time now with very few problems.
However, recently the timeline just started crawling along, and is
starting to affect our work.
Now, two things happened at around about the same time that could have
caused this, so I'd like some ideas on which one it might be
On Thu, 2006-03-16 at 19:06 +, Robert Hunter wrote:
On Thu, 2006-03-16 at 12:47 -0600, Russ Brown wrote:
We have been using trac for some time now with very few problems.
However, recently the timeline just started crawling along, and is
starting to affect our work.
Now, two things
On Fri, 2006-03-17 at 20:06 +0100, Christian Boos wrote:
Russ Brown wrote:
On Thu, 2006-03-16 at 14:16 -0600, Russ Brown wrote:
I believe the command is:
$ trac-admin resync /your/trac/env
Thanks! I knew I remembered seeing something like this before.
OK, I've run
On Fri, 2006-03-17 at 13:26 -0600, Russ Brown wrote:
What would be very valuable here is to know what was the last revision
for which the timeline was 'fast'.
You could setup a test server on the same repos that is showing the pb,
then do a dichotomic search to find the culprit rev
On Tue, 2006-03-28 at 15:40 -0500, [EMAIL PROTECTED]
wrote:
As I said, I'm a big fan of Roundup's concept of the nosy list. Basically
it's a list of email addresses to be notified about changes to a ticket.
Whenever a user makes any change to a ticket, they are automatically added
to the
On Mon, 2006-04-03 at 11:11 -0400, Sommers, Elizabeth wrote:
From my boss:
I want Trac to use files in Subversion (or any full WebDAV service) as its
store of issues and their associated data (attachments, audit trails, etc.)
Look up SubIssue on tigris.org. Subversion is really a
Hi,
There is increasing pressure within our company for a ticketing system
that will do what I know the new Flexible Workflow will do. Is there any
idea as to how long it will be before this hits trunk? We run off trunk
but would rather not have to deal with managing patches on top of it if
it
On Wed, 2006-07-12 at 10:24 -0400, Matthew Good wrote:
On Wed, 2006-07-12 at 08:43 -0500, Russ Brown wrote:
Anyway, the pressure is building, so any estimate would be helpful.
The workflow changes are scheduled for release in 0.11, so they'll be
merged into the trunk sometime after the 0.10
On Thu, 2006-07-13 at 14:28 +0200, Manuzhai wrote:
Thanks. So we could be looking at 4 weeks before it gets merged to
trunk? That would be lovely. :)
If you have no qualms about running trunk, why don't you just run the
workflow branch?
How frequently are changes to trunk merged to the
On Wed, 2006-08-09 at 18:09 -0400, Gary Oberbrunner wrote:
zdennis wrote:
Russ Brown wrote:
On Wed, 2006-08-09 at 14:00 -0400, Gary Oberbrunner wrote:
Hershel Robinson wrote:
As far as DB support, we know and use MySQL. Presently 4.1 but we plan
to upgrade to 5.1 as soon
22 matches
Mail list logo
