Launchpad itself

Need some fixes made to retain historic information.

Asked by Michael B. Trausch

On the AllTray project, in the historic-releases series - https://edge.launchpad.net/alltray/historic-releases - I would like to know if it is possible to make the “Date Released” match the historical reality. There are 24 historic revisions there by the previous maintainer which I have manually imported from its history at Sourceforge, and I'd like to know if the releases can have their date released modified to match when they were released. The time of day doesn't really matter, should probably be 12:00 UTC (noon) on each day so that the date is the same (nearly) everywhere.

The changelog is currently available at http://alltray.sourceforge.net/changelog.html which has the date for each release; the same information is available in tabular form (with time stamps) at https://sourceforge.net/project/showfiles.php?group_id=123652&package_id=135117 if that sort of thing can be done. If the information needs to be in a different format, please let me know that too and I can do that.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Curtis Hovey
Solved:
Last query:
Last reply:
Revision history for this message
Michael B. Trausch (mtrausch) said : 		#1

Any idea whether this is possible? Is this request unreasonable in some way? Just curious, it's been idle for a bit.

Revision history for this message
Curtis Hovey (sinzui) said : 		#2

This cannot be done, but your use case illustrates that it it should be done. The problem is that the "Date Released" is actually creation date of the record. We do need a true release date for projects that track the upstream projects, or that migrate to launchpad.

Someone is working on the ProductRelease model at this time. We will estimate if we can get this added for the next DB change.

Revision history for this message
Michael B. Trausch (mtrausch) said : 		#3

My apologies, I am slightly confused by your response, Curtis. When you say that you'll estimate if this can be added for the next DB change, do you mean the release dates for this instance, or are y'all going to be creating the infrastructure soon by which someone like me can specify dates when releases are uploaded? If the latter, will the ability to modify be present, or would that require LP admin intervention? And, any idea when those sorts of things could be done? And lastly (a lot of questions in a response, I know) do you mean that you'll be asking a DBA to make changes?

Again, sorry about being confused and probably annoying.

Revision history for this message
Best Curtis Hovey (sinzui) said : 		#4

I mean I want to close the bug I linked to your question. I think every project owner should have control of their release dates. We are currently working to link releases to milestones, and provide better delete and edit features. This is planned for 2.2.2 (2009-02-25). The changes involve database changes, and I want to add date_releases to the list of changes soon.

Revision history for this message
Michael B. Trausch (mtrausch) said : 		#5

Thanks Curtis Hovey, that solved my question.