Re: [th-users] Upgrade to Trac 0.12
Hi. I noticed that the testbed home page is not filtering the results correctly (each section lists all of the plugins in trac-hacks.) Uh, good catch. That indeed is not the intended behaviour and needs to be fixed. May I ask you to file a ticket for that against the component TracHacksPlugin, please? I'll then look into the issue. Bye, Mike ___ th-users mailing list th-users@lists.trac-hacks.org https://lists.trac-hacks.org/mailman/listinfo/th-users
Re: [th-users] Upgrade to Trac 0.12
Hello, I created the ticket here. I am looking into this and will try to submit a patch in a couple minutes. http://trac-hacks.org/ticket/7742 Cheers, Russ - bobbysmith007 On 9/28/2010 8:04 AM, Michael Renzmann wrote: Hi. I noticed that the testbed home page is not filtering the results correctly (each section lists all of the plugins in trac-hacks.) Uh, good catch. That indeed is not the intended behaviour and needs to be fixed. May I ask you to file a ticket for that against the component TracHacksPlugin, please? I'll then look into the issue. Bye, Mike ___ th-users mailing list th-users@lists.trac-hacks.org https://lists.trac-hacks.org/mailman/listinfo/th-users
Re: [th-users] Upgrade to Trac 0.12
On 09/27/2010 06:40 AM, Michael Renzmann wrote: Hi. I've then started to implement a cache for these things, so that the rendering happens only once, but got stuck somewhere in the middle. If I remember correctly, the latest state of that work is not yet available in the repository. Anyway, Trac meanwhile implements its own cache implementation, which is much better than what I came up with and which thus should be used for our purposes. I have to look at that stuff again. So, Trac 0.11 doesn't have this cache, so we won't get any improvement there, but why on 0.10 this works faster?? Well, I think in the end the speed issues are caused by Genshi. It's a known fact that Genshi is generally a bit slower than Clearsilver. In addition, there have been a lot of changes in how the hacks listings are generated (just compare the hacks list on both, the live and the testbed site). Maybe the homepage should not list all hacks then but link to [a] extra page(s)? Caching the list and especially the descriptions, at least somehow, would be essential anyway. Debian guys are strange - see the list of bugfixes at http://svn.apache.org/repos/asf/subversion/tags/1.6.12/CHANGES - I do not know what are they thinking about leaving 1.5.1 for ordinary folks. I run backported version on Lenny without any problems. That's Debian policy, I think - once stable is stable, the packages are not updated to new program versions. Of course that means you won't run top-notch versions on your Debian server, but you can be sure that your server remains stable and that configuration changes and other hickups, which may result from upgrading packages to a new program version will not occur unless you upgrade to the next new stable. Personally, I prefer this scheme over running a production server on the bleeding edge :) Yeah, Debian's two versions: either unstable or outdated ... I agree, it doesn't have to be bleeding, but I ran in the trouble under my Ubuntu installations (which is Debian based) where I had to manual compile it to get 1.6. It is a major upgrade from upstream, so it should be supported. I went from Gentoo to Ubuntu to avoid compiling. :-) Another example was this thing with gvim which spamed the console with hundreds of trivial messages at start-up where they refused to backport the also trivial fix, released just in the week after the official release. All in the holy name of stability. Regards, Martin ___ th-users mailing list th-users@lists.trac-hacks.org https://lists.trac-hacks.org/mailman/listinfo/th-users
Re: [th-users] Upgrade to Trac 0.12
On Mon, Sep 27, 2010 at 11:13 AM, Martin Scharrer mar...@scharrer-online.de wrote: I've then started to implement a cache for these things, so that the rendering happens only once, but got stuck somewhere in the middle. If I remember correctly, the latest state of that work is not yet available in the repository. Anyway, Trac meanwhile implements its own cache implementation, which is much better than what I came up with and which thus should be used for our purposes. I have to look at that stuff again. So, Trac 0.11 doesn't have this cache, so we won't get any improvement there, but why on 0.10 this works faster?? Well, I think in the end the speed issues are caused by Genshi. It's a known fact that Genshi is generally a bit slower than Clearsilver. In addition, there have been a lot of changes in how the hacks listings are generated (just compare the hacks list on both, the live and the testbed site). Maybe the homepage should not list all hacks then but link to [a] extra page(s)? Caching the list and especially the descriptions, at least somehow, would be essential anyway. Compile page into static HTML and regenerate it when reflected information is changed. Just need a list of events when this should be done. Like: 1. added/removed tags 2. added/removed hack Anything else? Yeah, Debian's two versions: either unstable or outdated ... I agree, it doesn't have to be bleeding, but I ran in the trouble under my Ubuntu installations (which is Debian based) where I had to manual compile it to get 1.6. It is a major upgrade from upstream, so it should be supported. I went from Gentoo to Ubuntu to avoid compiling. :-) Another example was this thing with gvim which spamed the console with hundreds of trivial messages at start-up where they refused to backport the also trivial fix, released just in the week after the official release. All in the holy name of stability. These versions are stable only when users report the issues, but Debian tracker suxx so greatly that I don't report anything anymore (unless the server is down or hacked). If nobody reports - there is a feeling that everything is ok, but that's not always true. Yes, this at least keeps flaky Linux package/binary-dependency system user-friendly, but this greatly outdated. I doubt there a could be a policy of common sense to solve this Debian problem, so we have to live with it until there will be a better OS, or social-oriented tools, where users can actually influence backporting and upgrading process. It could be Ubuntu, but GPL suxx, so not many professionals want to make their hands dirty with code they won't be able to copy/paste in some future project even with due attributions. -- anatoly t. ___ th-users mailing list th-users@lists.trac-hacks.org https://lists.trac-hacks.org/mailman/listinfo/th-users
Re: [th-users] Upgrade to Trac 0.12
Well, I think in the end the speed issues are caused by Genshi. It's a known fact that Genshi is generally a bit slower than Clearsilver. In addition, there have been a lot of changes in how the hacks listings are generated (just compare the hacks list on both, the live and the testbed site). Maybe the homepage should not list all hacks then but link to [a] extra page(s)? Caching the list and especially the descriptions, at least somehow, would be essential anyway I noticed that the testbed home page is not filtering the results correctly (each section lists all of the plugins in trac-hacks.) This is causing there to be maybe 5-6 times as many links as necessary. Perhaps it will be responsive enough when we are only displaying the list of links once? Cheers, Russ ___ th-users mailing list th-users@lists.trac-hacks.org https://lists.trac-hacks.org/mailman/listinfo/th-users
[th-users] Upgrade to Trac 0.12 (was: Re: Track-Hack Website and SVN down)
Hi. Action items I found: * Update/rewrite the NewHacksMacro to 0.12 and Genshi templates That already happened in preparation of the originally planned upgrade to 0.11. The functionality of that macro is now integrated in the TracHacksPlugin. You can see the current state of what has been done for the upgrade so far over at http://trac-hacks.org:81/. It's a fully-featured testbed installation, based on a (just updated and thus now recent again) copy of the original database and subversion repository of the live trac-hacks.org website. It makes use of the live t-h.o authentication information - means: you can use your normal t-h.o login, but take care that when you change your password there this will also affect your login on the normal t-h.o site. All other changes you do in the testbed - such as wiki page changes, registering new hacks, committing to the repository, ... - won't have any affect on the normal t-h.o site, however. The main issue that prevented me from performing the upgrade to the live t-h.o is: speed. You will notice it when you visit places in the testbed installation which present a list of hacks, such as the WikiStart page: it's painfully slow. IIRC I've investigated the reason for the issue and found that rendering the links to each hack's wiki page and tag pages is pretty time consuming. I've then started to implement a cache for these things, so that the rendering happens only once, but got stuck somewhere in the middle. If I remember correctly, the latest state of that work is not yet available in the repository. Anyway, Trac meanwhile implements its own cache implementation, which is much better than what I came up with and which thus should be used for our purposes. I have to look at that stuff again. * Test TracHacksPlugin with 0.12 (I installed it and imported all TH wiki pages, but it didn't list any hacks. Maybe that's a simple installation/configuration issue) I guess so. That functionality depends a lot of tags, which are most probably missing in the imported wiki pages. * Upgrade from TracBlogPlugin to FullBlogPlugin * Find a replacement for the now dysfunctional 'html' macro to e.g. show newflash divs. Done, see testbed. * Also: Upgrade subversion server/repository to 1.6.x I'll set that on my list. However, this step requires the use of packages from Debian Backports, since Lenny usually comes with 1.5.1. By the way: what is the benefit of the new version for our purposes? Bye, Mike ___ th-users mailing list th-users@lists.trac-hacks.org https://lists.trac-hacks.org/mailman/listinfo/th-users
Re: [th-users] Upgrade to Trac 0.12
On 09/26/2010 05:21 PM, Michael Renzmann wrote: Hi. Action items I found: * Update/rewrite the NewHacksMacro to 0.12 and Genshi templates That already happened in preparation of the originally planned upgrade to 0.11. The functionality of that macro is now integrated in the TracHacksPlugin. I saw this in the meantime. The new implementation looks quite good. * Also: Upgrade subversion server/repository to 1.6.x I'll set that on my list. However, this step requires the use of packages from Debian Backports, since Lenny usually comes with 1.5.1. By the way: what is the benefit of the new version for our purposes? It is not THAT important, but I had some problems when trying to do some branch merging. I will check out the testbed. Is this now for the update to 0.11 or 0.12? The testbed runs on 0.11, doesn't it? Anyway the step between 0.11 and 0.12 would not be this big than the step to 0.11. Best, Martin ___ th-users mailing list th-users@lists.trac-hacks.org https://lists.trac-hacks.org/mailman/listinfo/th-users
Re: [th-users] Upgrade to Trac 0.12
Hi. By the way: what is the benefit of the new version for our purposes? It is not THAT important, but I had some problems when trying to do some branch merging. Ok. I will check out the testbed. Is this now for the update to 0.11 or 0.12? The testbed runs on 0.11, doesn't it? Anyway the step between 0.11 and 0.12 would not be this big than the step to 0.11. The testbed runs on 0.11.6 and was originally prepared for testing the upgrade procedure (and implementing the steps required for the upgrade as shell script to automate the required steps and thus keep the down-time low for the real upgrade, once it happens). The testbed will have to be switched to Trac 0.12 now, of course - which will be one of the next steps I'll take here. Bye, Mike ___ th-users mailing list th-users@lists.trac-hacks.org https://lists.trac-hacks.org/mailman/listinfo/th-users
