-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Date of release missing #78
Comments
hey can you tell where the issue located |
@quozl the link you have provided contains version dates in the changelog. They give an idea of what was the latest release version and its date. What exact date do you want added in this as well ? |
The issue and opening comment talks about the date of the release, the case you've pointed out seems to be one case where dates where included in the changelogs, but it doesn't apply for a host of other activities, which is why the issue is open. Each page shows the version released, but not the date the version was released, the changelogs usually don't contain the date of the release but the changes of the release. Hope this helps. |
The dates in the NEWS file are in the wrong order, and don't include the releases beyond a certain point. That's not a problem with the NEWS file, but a problem with assuming the NEWS file is useful for giving the release date. Abacus, for example, only has version numbers in descending order. |
Thank you, I understand now! Can you please point out to the files where I can add the latest version release dates in the info section. |
No, that won't fix the problem, as developers made and make activity releases without updating the NEWS file. Another method will be needed. By preference using the data or metadata already known to the application. You probably have to understand the entire activity release process, and the step that involves aslo-v4, before designing an intervention. |
On an info page it isn't possible to tell how old a release is. There is no date or number of days.
The text was updated successfully, but these errors were encountered: