Team Chat Logs

April 18, 2010

2010 3
Mo Tu We Th Fr Sa Su
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30    
<< <   > >>

[04:19:43.389514]<hasienda>rblank: I've published some patches yesterday, but there is some debugging work to be done, before I feel custom fields ready for beta-testing. Do you have a chance to look into it anytime soon.
[04:20:00.588038]<hasienda>rblank: I know, there must be much to do for the upcoming release of Trac 0.12.
[04:20:43.447486]<rblank>hasienda: That unfortunately won't be possible in the next few days, due to 0.12.
[04:21:16.147659]<rblank>hasienda: Also, we're going to discuss the development mode for 0.12.x and 0.13 in the next few days, so I'm not sure yet if your patches will make it into 0.12.x or 0.13.
[04:22:11.957417]<rblank>hasienda: Is it correct that the repository containing your patches is a Mercurial queue against my trac-trunk-wc?
[04:23:30.823886]<hasienda>rblank: yes, but not tip currently. Still at the revision equal to Trac SVN 9443 with focus on debugging.
[04:24:03.977018]<rblank>hasienda: Ok, that gives me a strong incentive to start looging into MQ and finally understand how it works :)
[04:24:13.559206]<rblank>s/looging/looking/
[04:24:14.113374]<evil_twin>rblank meant: hasienda: Ok, that gives me a strong incentive to start looking into MQ and finally understand how it works :)
[04:25:30.178096]<hasienda>rblank: It took me only 5 days to understand both HG and MQ, so should be fairly easy for your. :-)
[04:30:18.710034]<hasienda>rblank: mastering MQ is not pre-requisite for looking at the patches, since they can be extracted from repo and used with trunk source like with any other patch made with 'diff -u'.
[04:35:19.738497]<hasienda>rblank: Still I don't know, how importent it is to be always up to Trac SVN HEAD for this development. Would you tell me please, at least your opinion.
[04:35:39.818074]<hasienda>rblank: ?
[05:01:46.569518]<rblank>hasienda: About working against HEAD, it's not important to *always* be on HEAD. Patches usually apply just fine even after many revisions.
[05:02:39.760919]<rblank>hasienda: So it's enough to rebase the changes from time to time.
[05:03:10.670063]<rblank>hasienda: I tend to rebase my changes after every significant bit of work, but that's only because Mercurial makes merging so easy.
[05:04:02.378695]<hasienda>rblank: Good, so I'll stay with watching for changes in the trac/ticket dir and trac/util/datefmt.py so far.
[05:04:26.943171]<hasienda>rblank: May I ask what tool you use for merging?
[05:04:36.015770]<rblank>hasienda: Exactly. Rebasing is only really required if files you modified are changed on trunk as well.
[05:05:05.632377]<rblank>hasienda: Err... None actually. I work with the conflict markers left in the files, the <<<<< ===== >>>>> stuff.
[05:06:42.695407]<hasienda>hasienda: I see. Than I'm still too much of a gui fan boy :-( I found kdiff3 giving me better orientation while merging long files.
[05:11:18.705270]<hasienda>rblank: Mercurial does support merging often quite well indeed, as long as you don't miss --addremove as I did at the start.
[05:12:21.939721]<hasienda>rblank: So my first try was a big failure, missed all new files after merging 23 revisions by hand. You may guess my feelings a that time. Your offer to clone from your repo was a saver then.
[05:15:44.881465]<rblank>Gotta go. Catch you later.
[07:00:14.108478]<scfe>after updating the German po file, there are a lot of unused translations
[07:00:21.889187]<scfe>can I rely on babel and delete them?
[07:00:32.313533]<scfe>or does babel not find all?
[07:03:06.786013]<scfe>could this be because babel picked up Genshi 0.5 instead of 0.6dev?
[07:15:15.700897]<scfe>may I assume that the french translations are well-maintained?
[07:15:29.850317]<scfe>so a msgid which does not appear there can be deleted?
[07:15:46.746117]<hasienda>scfe: from what I know yes.
[07:16:36.225391]<hasienda>scfe: German is in suprisingly bad shape, wanted to do something on that myself anytime soon.
[07:17:16.101096]<hasienda>scfe: will you contribute, or is it just for yourself?
[07:17:17.520704]<scfe>hasienda: Ok, I'll set up a hg repo so we can work together on that
[07:17:26.485893]<scfe>hasienda: I'll send patches of course
[07:17:30.725535]<scfe>though my time is limited
[07:17:49.760690]<scfe>though this depends on how active the vulcano is... *g*
[07:18:12.142403]<hasienda>scfe: mine too, working on custom time field most of my spare time.
[07:18:13.139341]<scfe>but I won't have the time to fix all translations
[07:19:09.107337]<hasienda>scfe: I'm not even associated with the guy coordinating translation effort for German, guess both of us should contact him.
[07:19:28.330221]<scfe>I'll just start translating
[07:19:36.573448]<scfe>and send an email this afternoon
[07:19:49.305099]<scfe>(have to do a some more releases today)
[07:20:52.501526]<hasienda>ok, go for it. still would be happy to hear about any progress here, if you could arrange so.
[07:24:11.981102]<scfe>sure
[07:24:24.647550]<scfe>I'll just set up a bitbucket repo so we can collaborate
[09:13:40.625762]<scfe>hg mirror from svn: http://bitbucket.org/felixschwarz/trac
[09:14:02.559349]<scfe>patch queue for german translation: http://bitbucket.org/felixschwarz/trac-l10n-de
[11:27:57.720430]<hasienda>scfe: have seen your HG repo @ bitbucket.org, following you now.
[11:30:39.642666]<hasienda>scfe: I see, that you are the one how wrote some recommendations into Trac enhancement ticket #1942 for custom time field support too. Thanks.
[11:35:01.233868]<hasienda>scfe: I'll test and fix my patches this evening for another revision of custom time fields.
[11:37:21.511246]<hasienda>scfe: This evenings release should work reasonably well even for someone willing to do some beta-testing. I think, critical malfunctions are gone, just minor and cosmetic fixed now.
[12:32:18.316992]<pb30>when using ticketquery, is there an easy way to make the count displayed a link to the results page?
[12:48:03.708390]<hasienda>pb30: since this is no documented functionality, this would certainly require to change some code, so the answer is No.
[12:48:31.495073]<hasienda>pb30: However, this sounds like a reasonable enhancement
[12:49:22.906793]<pb30>what about a column for the last person who changed a ticket, i know in the sql its ticket_change.author, is this available for tracquery's?
[13:11:30.717637]<hasienda>pb30: sorry, but the answer is another No: trac/ticket/query.py does know about 'ticket' and 'ticket_custom', but no other db table.
[13:12:35.584606]<hasienda>pb30: but a custom report might work (no experience with this so far).
[13:13:14.246556]<pb30>yeah im using a custom report, but wanted to make a status/dashboard page that included the last 10 tickets modified by a specific user
[13:13:58.191541]<scfe>is t.e.o. down?
[13:14:19.435859]<scfe>sorry for the noise - seems to work, just extremely slow
[13:16:12.928448]<scfe>hasienda: If you want to improve the translation, please just pull and create a patch
[13:16:27.408210]<scfe>I'm happy to hand out commit access to my tree to everyone interested
[13:21:09.077988]<hasienda>trying to POST changes to Trac wiki at t.e.o. I get timeouts too, looks dead.
[13:37:22.128798]<hasienda>now http://trac.edgewall.org/ returns: 500 - Internal Server Error
[13:51:14.987415]<infid>is it possible to delete old tickets? tryin to read the faq right now but it's not loading for me, site may be down
[14:08:30.807056]<infid>a it's just trac-admin remove
[14:37:57.748655]<infid>why doesn't this work: trac-admin milestone remove test
[14:38:12.637876]<infid>it says *** unknown syntax: remove 'test'
[14:44:21.384845]<infid>nm i forgot to specify the ful path to the env
[16:08:06.460563]<hasienda>t.e.o. working again, thanks.
[21:22:03.535827]<tclugg>doki_pen: ping? Having isssues with DateFieldPlugin as per issue #5452.