Add release management UI [#373175]

How can we remove multiple versions of the same package?
Shouldn't it keep only the -dev and the last major versions for exporting?
This is a nightmare to understand what is really important and it is cluttering the database and waste our small team efforts probably with useless strings.

To better understand what I mean look at the screenshot attached representing our "Drupal" translation export section.

Comment	File	Size	Author
	l10n.png	90.71 KB	lopolencastredealmeida

Comments

Comment #1

gábor hojtsy

he/him

Hungarian

Hungary

commented 12 February 2009 at 09:35

For Drupal core, it might make sense to only keep the latest version, however, removing older versions basically discontinues support for those versions, which we might not want (there are at least subtle string changes from time to time).

For contributed modules it is a whole different world, 5.x-1.x might be a supported branch, while 5.x-2.x has new feature development, etc. So eventually, it comes down to the translation team to decide which ones to focus on, because contributed module maintainers use the version numbers in different ways.

Comment #2

gábor hojtsy

he/him

Hungarian

Hungary

commented 18 January 2010 at 12:51

Title:	Multi version of the same package	» Add release management UI
Component:	Code	» Miscellaneous
Priority:	Critical	» Normal

Retitling to be more specific. We currently have a "Start over" feature for a full project as well as a "Delete" feature for a complete project. We do not have that yet on a per-release or multi-release basis, so you can keep some of the releases, but not all. We'd need to build out the release management UI and possibly add automated ways as well to remove old releases, when newer ones are available.