Description of problem: The stats of past versions of Fedora are influenced from the stats of the current version. An example is the Release Notes document. Expected results: The stats should be indipendent release by release. If their value change inappropriately they loss their meaning. Should be a solution for document (packages) that are not branched the creation of new module definition?
Francesco, could you please be more specific on what the problem is, and where to see it in action?
Yes Dimitris, in the teams or language pages, we can see the stats for the releases F8 and F9, like in http://translate.fedoraproject.org/languages/it as you can see in http://translate.fedoraproject.org/languages/it/fedora-9 and http://translate.fedoraproject.org/languages/it/fedora-8 the Release notes doc is complete at 70% for all the releases, but it should be 100% for F8 and 70% for F9. I have some doubt if this case is applicable to others modules too. And another thing, while the team is working for F9, the stats for F8 and F9 go forward together. So why are we show all the modules for 2 releases? I think we should show only the current version (rawhide) and for the past version only the branched modules or modules that was splitted (like Release notes).
OK, I understood now. The problem is specific only for some Documentation modules. These modules use directories to distinguish between branches, as you can see from http://translate.fedoraproject.org/module/docs-release-notes. Damned Lies handles Releases in a branch-way. For example, Fedora-9 for module X has the "HEAD" branch but for Fedora 8 it uses the "fedora-8" branch. However, these Docs modules only use one branch: "HEAD". That's why the releases page cannot distinguish what we ship with each release. Two ways to fix it: 1. Change how Fedora handles Docs. Instead of having branches in sub-dirs, have them in separate VCS branches. 2. Extend Damned Lies to be able to do releases using directories instead of only branches. Something like `<release name="fedora-9"><module id="foo" dir="bar" /></>`.
Resolved with migration to git and using real branches.