Making WordPress.org

Opened 8 years ago

Closed 7 years ago

Last modified 7 years ago

#2644 closed defect (bug) (fixed)

Last updated should update when trunk is stable_tag & trunk files altered

Reported by: dd32's profile dd32 Owned by: dd32's profile dd32
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)

#1 follow-up: @Ipstenu
8 years ago

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?

#2 @Otto42
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.

#3 in reply to: ↑ 1 @SergeyBiryukov
8 years ago

Replying to Ipstenu:

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.

Related: #3010

#4 @tellyworth
7 years ago

  • Keywords 2nd-opinion added

#5 @dd32
7 years ago

  • Owner set to dd32
  • Resolution set to fixed
  • Status changed from new to closed

In 6073:

Plugin Directory: Bump last_updated when the built ZIP changes, which may be as simple as a readme update.
This restores the behaviour of bumping the Tested up to header to allow plugins to avoid the 2 year unupdated banner.
This also fixes the expectation of last_updated being reflective of the last development changes, for example when the plugin uses trunk as it's stable_tag.

Fixes #2644

#6 @dd32
7 years ago

In 6074:

Plugin Directory: Fix a reversal of parameters in [6073] after a last-minute fumble.
See #2644

Note: See TracTickets for help on using tickets.