[Trac-dev] Re: Akismet ate my change to TracUsers wiki page
On 9/19/06, Lloyd D Budd [EMAIL PROTECTED] wrote: I thought I would give a little love to http://trac.edgewall.org/wiki/TracUsers by first alphabetizing the A's. Akismet ate it as spam. See attached for the diff. I am glad I was not really ambitious ;-) I would like to add that a ticket I was creating the other day was rejected as LED spam. This is really annoying... Could less intrusive (fewer false positives) methods be used to prevent spam? Regards, MAnuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev -~--~~~~--~~--~--~---
[Trac-dev] Re: Time to get 0.10 out the door?
On 9/20/06, Jonas Borgström [EMAIL PROTECTED] wrote: What do you guys think about releasing 0.10 on Monday and maybe a rc1 release tomorrow or on Friday? Good idea (about damn time is another way of putting it). Maybe just #3753? It's like a three-line thing, anyway. Doesn't really matter either way, of course. Regards, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev -~--~~~~--~~--~--~---
[Trac-dev] Re: Actual Roadmap (0.10 and 0.11)
On 10/6/06, Christian Boos [EMAIL PROTECTED] wrote: Eh, for now it's quite adequate, as actually we (at least I) don't know if they will be part of 0.12 or not, in the end. If development speed remains, the first items in the list would be completed quite soon, and there will still be time to do more, like the WorkFlow merge, especially given the fact that this can be started in parallel anytime now (Alec?)... I think that if development speed remains, we should just get 0.11 out quicker, rather than piling on new features. The 0.10 release cycle was endless... Regards, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev -~--~~~~--~~--~--~---
[Trac-dev] Re: POLICY - Ticket Descriptions should be treated as original content
On 12/4/06, Brad Anderson [EMAIL PROTECTED] wrote: Can't wait for that. Can Mr. Lazaridis just be banned, from mailing list and t.e.o? He's undermining progress of the Trac project. http://producingoss.com/html-chunk/difficult-people.html Regards, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Security branch (merge to trunk?)
On 1/12/07, Christian Boos [EMAIL PROTECTED] wrote: So again, about the merge in trunk: - I'd like we sort out the above first - I'd like to merge my 3 other branches (blame and the 2 -tmp ones) before ;) And after that, maybe there should be some effort towards releasing 0.11? It seems merging these branches pretty much fixes all of the goals stated for 0.11 in the roadmap... Regards, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Merging of the Blame Branch
On 1/12/07, Christian Boos [EMAIL PROTECTED] wrote: Looks like we're ready for a merge... I upped my install to r4561 and tried to annotate one of my files, but it merely gained a completely empty column on the left of the source display. Any ideas on how to fix/debug this? Regards, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Merging of the Blame Branch
On 1/13/07, Christian Boos [EMAIL PROTECTED] wrote:
Ah, that's a different beast then.
First the above message should have showed up in the title of the th
corresponding to the blame column.
Right, I'm seeing that now (it just shows when I hover the column
header, not when I click it -- in fact, I think clicking the header
probably prevents it from showing).
Then, look again in the log, you should see the actual URL used for the
ra_local session, because of the following statement:
self.repos.log.info('opening ra_local session to' + repo_url)
Can you 'svn ls' that URL?
Since I'm using a scoped repos, I applied your patch first. After
that, it still didn't work.
[EMAIL PROTECTED] nts $ tail log/trac.log
2007-01-13 18:27:56,866 Trac[svn_fs] INFO: opening ra_local session
tofile:var/svn/xm
2007-01-13 18:27:56,949 Trac[api] WARNING: Can't use annotator
'blame': svn blame failed: ('' is not a file, 160017)
[EMAIL PROTECTED] nts $ svn ls file:var/svn/xm
aycha/
equilex/
hebe/
(...)
[EMAIL PROTECTED] nts $
Oh, are you using a scoped repos?
If yes, try this patch:
Index: trac/versioncontrol/svn_fs.py
===
--- trac/versioncontrol/svn_fs.py(revision 4561)
+++ trac/versioncontrol/svn_fs.py(working copy)
@@ -672,8 +672,7 @@
annotations.append(revision)
rev = _svn_rev(self.rev)
start = _svn_rev(0)
-repo_url = 'file:///%s%s' % (self.repos.path,
- self._scoped_svn_path)
+repo_url = 'file:///%s' % self.repos.path
self.repos.log.info('opening ra_local session to' + repo_url)
from svn import client
try:
That's most certainly it.
So, what now? And it shouldn't it become file:///var instead of
file:var (though it obviously doesn't matter)?
Regards,
Manuzhai
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac
Development group.
To post to this group, send email to trac-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~--~~~~--~~--~--~---
[Trac-dev] Re: Merging of the Blame Branch
On 1/13/07, Christian Boos [EMAIL PROTECTED] wrote: So this might have been the reason... Let's try something else. I figured it out, I think. See [1] for the patch I came up with... The problem is with the way SubversionNode stores the repos scope. Instead of having a scope like SubversionRepository, which always starts and ends with /, its self._scoped_repos_path is run through _to_svn(), strips outer slashes. Therefore, the path that blame tries to work with doesn't contain a slash between the actual repository path and the actual file path within that repository. Regards, Manuzhai [1] http://manuzhai.nl/files/fix-scoped-blame.diff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Merging of the Blame Branch
On 1/13/07, Christian Boos [EMAIL PROTECTED] wrote: Actually, _scoped_repos_path used to start with a '/' in unscoped repositories and without in scoped repositories. I fixed that in http://trac.edgewall.org/changeset/4563, now blame should work in both cases (it does for me on Windows, at least). WORKSFORME, thanks! Regards, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Discussing two changesets
Hello all, I'd like to discuss two recent changesets with which I don't necessarily agree. The first is r4769 [1], which fixes issue #3421 [2]. This patch visually merges two or more consecutive changesets when the author and commit messages are the same, but I'm not sure this is a good idea. In my opinion, the timeline is important in that it serves as a good overview of what's been happening to a project, but with this patch, information on changesets can is conflated. Of course, having many commits with a similar/the same message is in most cases just a Bad Idea, and I don't like how Trac codifies that this is okay. Also, with the current code this is not a preference, so I can't easily turn this behavior off. I would suggest that the changeset be entirely reverted, so the timeline just displays the changesets as-is (my preference), or that this is turned into a preference. Either way, I feel this feature is somewhat orthogonal to Trac's KISS principles. The second is r4786 [3], which fixes issue #1925 [4]. Now, I'm actually the reporter on this bug, so obviously I care about this little thing (I have maintained my working copy with a patch that fixes this for 2 years). I think it's an unobtrusive feature that makes the reports easier to use at the expense of an optional extra preference. I recently posted my patch to the comments since a committer (cboos) finally showed some interest in the ticket (it was rejected by cmlenz initially because he figured that if I just wanted the open tickets list I could get it by disabling the reports module and use the query module and its default config). In r4786, cboos fixed the ticket by making his own version of my patch. Instead of changing the navcontributor in the reports module to check for, then link to, the default_report option value, he chose to have a default -1 value for the option, then make /report/-1 link to the list (instead of /report, as before) and make /report link to the default report. I think this is a bad idea for two reasons: (a) -1 is kind of an ugly magic value that suddenly does something different, which should not be exposed to the URL interface (and preferably not to .ini file either, I'd prefer having something None-like or just leaving the default_report option out if it's not wanted). The other reason (b) is that this changes links to the report list and the default report from before: http://trac.xavamedia.nl/nts/report becomes http://trac.xavamedia.nl/nts/report/-1 http://trac.xavamedia.nl/nts/report/1 becomes http://trac.xavamedia.nl/nts/report (Provided 1 is the default_report.) So I'd like to ask the list to consider these sentiments. If this is just whining, I'll just shut up (about these issues) and maintain my own patches. If you agree, however, may be speak up and discuss how minor improvements should be implemented. Regards, Manuzhai [1] http://trac.edgewall.org/changeset/4769 [2] http://trac.edgewall.org/ticket/3421 [3] http://trac.edgewall.org/changeset/4786 [4] http://trac.edgewall.org/ticket/1925 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Ticket #2821
On 5/11/07, Eli Carter [EMAIL PROTECTED] wrote: I've implemented a solution to http://trac.edgewall.org/ticket/2821 in https://svn.edgewall.com/repos/trac/sandbox/ticket-2821 (This builds on work done by cboos earlier.) I quickly looked through the changes on the branch, but it seems to me there are a lot of changes unrelated to the #2821 problem. Shouldn't those just be on trunk and merged to the branch? And is there some sort of design document on what you're going to implement to fix #2821? Regards, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: WorkflowUpgrade sandbox
Eli, I upgraded to trunk this morning, and it seems to work allright. The message I got at trac-admin upgrade, though, has two spaces between every sentence, which I find a bit ugly. The upgrade to basic-workflow seemed to have worked as well. I've made a patch, though, to make it just a little friendlier... Include an error message when no argument is given (instead of bombing out with an exception, which, as the code says, is not that nice, and give some feedback about what it's doing. See [1]. Regards, Manuzhai [1] http://manuzhai.nl/files/friendly-migration.diff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: 0.11 ?
On 6/28/07, Emmanuel Blot [EMAIL PROTECTED] wrote: IMHO, Trac really needs a 0.11 release - soon. What's your opinion? I agree, if only because we can give everyone Workflow and move everything over to Genshi. Regards, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Any plan to support BBAuth from Yahoo ?
On 8/27/07, TJ Yang [EMAIL PROTECTED] wrote: Will you code TracBBAuth for gift ? I am lazy but willing to give out gift (say from amazon.com) for people do the work. I might be willing to do this, if Noah is not up for it. Looks like it's not that hard. Regards, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Syntax Coloring Pointers
On 8/30/07, Dave [EMAIL PROTECTED] wrote: I should have specified, I'm using pygments currently, but it doesn't do the table layout in the same way. There's some kind of different hackery going on to coerce to the layout trac uses. I think pygments is just being called on each line... or something, haven't figured it out yet. I think the mimeview package is what you're looking for, probably in combination with some magic Genshi sprinkling. Cheers, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: What's gone wrong on the road to Trac 0.11
On 9/10/07, Christopher Lenz [EMAIL PROTECTED] wrote: 1) Too many changes with too much impact 2) Too many API changes without much benefit 3) Added bloat 4) Not enough testing 5) Not enough communication I have to say I agree with a lot of your points. In the past, I've expressed similar opinions on the mailing list and in IRC; most specifically that we should release sooner instead of adding more to the release. I also agree with the bloat/useless API's, specifically the whole context/security thing which I have looked at but haven't been able to grasp. Also, one of the important reasons I stopped maintaining the community buildbot for Trac was that the unit tests were always failing. Lastly, in my experience it's largely impossible to follow the development. I peruse the Timeline through RSS and track all the checkins from there, but there is often too little context to follow the high-level reasoning behind the changes. I'm assuming that some of that is discussed on IRC and I started idling in the channel, but there's just too much noise/friendly talk/discussion to keep up. I hope the Trac development can refocus, get the communication on the mailing list so more people can contribute, and that we can release 0.11 soon. Cheers, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Following the right road
On 9/24/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: could you pls clearly state what needs to be done iyo until release? backport genshi and release 0.10.6? Rupert makes the same point I was thinking about last night (and I think it merits its own thread). Now that there seems to be a consensus that the road was wrong, where are we going with 0.11 now? What needs to make it into 0.11, what API's need to be changed or refined or scrapped, without resorting to feature creep? Cheers, Manuzhai (just released my first plugin, feeling pretty good about it, too) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Following the right road
On 9/24/07, Christopher Lenz [EMAIL PROTECTED] wrote: The most important thing we need to fix IMHO is the trac.context API, and the ITimelineEventProvider/TimelineEvent API. The one feature that should really be moved out into a plugin is Clone Ticket. Okay, so where is the whole context going to go? What should it become? And does the ITimelineEventProvider just go back yielding tuples? Cheers, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Trac Authentication - first steps.
On 9/25/07, Ruben O [EMAIL PROTECTED] wrote: im following my first TRAC installation and setup. After solving few problems im trying to implement authentication to my TracStandalone web server. Assure that i have read all information about Authenticacion but i don't understand well or perhaps lack information for newbies users of TRAC. Even if you have read all the information, you should go to the [EMAIL PROTECTED] list. This list is meant for people who develop Trac itself. Cheers, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Context Refactoring
On 9/25/07, Christian Boos [EMAIL PROTECTED] wrote: Well, the point is to discuss a way to do fine grained permission in 0.11 until we get it right, so I don't see how this is rushed... Leaving what the point is for now, it seems to me that the point *should* be how to get 0.11 out the door, while only fixing what's really broken at this point (i.e. bad API's). This release cycle has taken way too long already... Cheers, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Fail to install yui js into /usr/share/trac/htdocs/js/yui/*
On 9/28/07, sirtoozee [EMAIL PROTECTED] wrote: So is there some way to auto-install 3rd javascript library, please someone give me advice, thanks a lot! My advice is to ask your questions on the trac-users list rather than trac-dev. trac-dev is only meant for Trac developers. Cheers, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: commit rights for osimons
On Nov 23, 2007 3:31 PM, Jeroen Ruigrok van der Werven [EMAIL PROTECTED] wrote: Sounds like a good idea to me. I have no vote, but I like the idea as well. Cheers, Manuzhai (djc) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Trouble in installing Trac
You shouldn't crosspost installation issues to the -dev list. Sending it to the trac-users list is sufficient. Cheers, Manuzhai On Nov 28, 2007 3:39 PM, [EMAIL PROTECTED] wrote: Hi all, I am new on Trac. I already let a message in the TracUser Group, because i get trouble in Trac Installation : I'am getting the following error in the admin.py ( after running the command python byte-compiling /usr/lib/python2.5/site-packages/trac/scripts/admin.py to admin.pyc File /usr/lib/python2.5/site-packages/trac/scripts/admin.py, line 17 from __future__ import generators SyntaxError: from __future__ imports must occur at the beginning of the file For information, i try to install Trac on Ubuntu ...(theoriccaly, i think i've all the installation requirements). Thanks in advance. Regards, Fabien. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Trac 0.11beta1 coming soon
On Nov 28, 2007 7:53 PM, Christian Boos [EMAIL PROTECTED] wrote: Before doing that though, I'd like to ask everyone to do some last minute testing, to be sure we won't release something that has some big flaws in it. Especially important would be the testing of the #5064 changes, as I was not able to do it fully myself. I've been running the latest Trac trunk on several boxes, seems to be working just fine for me. Cheers, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: THANKS - AUTHORS
On Dec 5, 2007 9:58 AM, Jeroen Ruigrok van der Werven [EMAIL PROTECTED] wrote: Does someone have an objection if I move the committers from THANKS to AUTHORS (or remove their entry from THANKS if already in AUTHORS). There's little need to keep duplicate information I think. :) Do you mean to imply the project doesn't thank its AUTHORS? (I'm about half-serious here.) Cheers, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: versioncontrol improvements (was Re: [Trac-dev] Re: 0.12)
On Dec 5, 2007 12:47 PM, Christian Boos [EMAIL PROTECTED] wrote: The single small incremental API change I want to make for 0.12 at this point is the one documented in #4900 (see http://trac.edgewall.org/ticket/4900#comment:4). We were just discussing this in IRC. I have been thinking about how to move the Trac UI more towards making it sensibly support both Subversion and Mercurial (and by extension, at least Bazaar and git). I have some ideas about this that need some more fleshing out, I think. Will see what I can do with the idea. Cheers, Manuzhai --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: Macro in heading not working?
Please ask this question on the trac-users list. http://groups.google.com/group/trac-users?hl=enlnk=srg Cheers, Manuzhai On Thu, Apr 3, 2008 at 2:09 PM, Kim Rasmussen [EMAIL PROTECTED] wrote: Hi! I need to insert some information, which has been pulled out of a database, in a heading using a custom macro. Unfortunately it doesn't seem to expand in a heading -- I just get [[WhatEverMacro(...)]] inserted in the heading. Does anyone know if there's a workaround? Thanks. Kim --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
[Trac-dev] Re: tentative 0.12.0 release schedule
On Sat, May 3, 2008 at 11:47 AM, Jeroen Ruigrok van der Werven [EMAIL PROTECTED] wrote: My current suggestion: beta 1 : 2008-10-01 beta 2 : 2008-10-14 rc1: 2008-11-01 rc2: 2008-11-14 (as needed) release: 2008-12-01 I think the cycle could be much shorter for than that. Instead of aiming to fix everything bug in the tracker, get i18n and MultipleRepositorySupport (which are supposedly both already in a fairly usable state), merge them, fix things up (including lots of small bugfixes, of course), and release in three months. Cheers, Dirkjan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Development group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~--~~~~--~~--~--~---
