> Andrea, Meir :-) > Thanks for your quick response... It's the Product Backlog with 210 > items, not the Release Backlog... but anyways, we're running Python > 2.5 and Trac 0.11.4 and we don't have a proxy on the network. If we > could get the load time down to 6 seconds that would be great! Is > there a setting that needs to be turned on for the cacheing? With Trac >= 0.11.3 the caching is already enabled, so you might have either a very slow hardware or some other issues, for example you may consider adding to the server also the mod_deflate (compressing everything which is JS, CSS, HTML) this will dramatically reduce the size of the page load...
If you implement a Release Backlog, the goal is for you to work one release after the next in the Release Backlog, that should contain less than the 210 tickets. Than if you have the option "strict" in the Product Backlog, the ticket you already assigned to the Release Backlog (setting the milestone in the Requirements) should not appear in the Product Backlog anymore. It is a workaround, basically is about partitioning the work on more backlogs to make each more fast and easy to manage ;-) > Thanks! HTH > Meir ANdreaT --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
