#2644 closed defect (bug) (fixed)
Last updated should update when trunk is stable_tag & trunk files altered
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Plugin Directory v3 - Future | Priority: | normal |
Component: | Plugin Directory | Keywords: | 2nd-opinion |
Cc: |
Description
Currently the Last Updated
field only gets bumped when the version number changes.
However, when a plugin is using trunk as their stable version, the last_updated field should probably change after a commit is made to trunk (but not to assets, branches, or unrelated tags).
Update notifications wouldn't be sent if an author using trunk as stable changed files without changing the version, but new users would get a different "version" of files - which is why I believe it should bump the updated date.
Change History (6)
#2
@
8 years ago
Could we not simply use "svn info" to get the last changed date of the directory where "Stable" is and consider that to be the last updated date? Seems like this would solve both problems. It also is what one previous incarnation of the directory did, though that has changed a few times.
I hate to suggest this but ... the last updated should change whenever the readme is updated, so that we can continue to allow people to bump the 'Tested up to...' value in the readme in order to indicate activity and compatibility.
Would it be possible to check if that value changed and bump the last update, or would that be too draining on resources?