I think, it is necessary to add a field is_active in table l10n_community_release (the Localization server scheme of data: http://drupal.org/files/issues/ls.gif)
1) The server of localization works with the version module only if value is_active equally try or 1
2) In other cases it ignores this version of the module.
3) The out-of-date projects translated lines should be removed (#203658: Delete abandoned projects).
4) From old version(is_active = 0) versions lines should not be taken repeatedly.
5) The projects marked as old not used in a "Connector for drupal.org" interface

An interface is necessary for a mark of projects is old.

Comments

brmassa’s picture

brmassa commented

Vasili,

good point. Well, you would be surprise if i tell you how many people are still running D4.7 and very old modules, so simply deleting/ignoring them i would recommend. BUT, i agree about having a filter or something to help translation groups to focus on latest stable versions.

regards,

massa

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Title: Improvement of the scheme of data » Add status column to releases (additionally to projects)
Version: 5.x-1.x-dev » 6.x-1.x-dev
Component: Code » Database
Category: feature » task

The database already has a status column for projects, and those projects which are disabled will not get new releases parsed or handled in any other way. We do not have such a control for releases, so revoking releases when a project is not revoked is not handled. What's the use case for that?

SebCorbin’s picture

SebCorbin commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
Issue summary: View changes
Related issues: +#2100597: Add a connector for www.drupal.org’s REST API

We should be able to fetch additional info about releases (stable or not, active or not) with the REST API from drupal.org now.

This will happen in 7.x though.