Opened 14 months ago
Last modified 11 months ago
#6419 new defect (bug)
In situ edits of readme does not update properly
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Plugin Directory | Keywords: | |
Cc: |
Description (last modified by )
Edited since this is a little bigger.
Originally:
If a plugin enables release notifications and later makes cosmetic edits to a plugin (such as bumping 'tested up to') _WITHOUT_ making a new version, the change will not be noticed or set live.
This results in developers asking plugins to remove the feature from their plugins.
Recommendation:
If an _active_ tag is changed, allow a release notification
Updated:
Making any edits to the readme without bumping versions results in nothing changing on the front end. This means it's a requirement to release new versions in order to update tested-up-to (for example).
Change History (3)
Note: See
TracTickets for help on using
tickets.
This was kind-of by design. The intention is that the release should not change after approved, even if the tag changes (which realistically, should never happen).
Unfortunately, as we all know though, plugins often need to update
tags
for readme changes..I would love if the fix for this wasn't to support tag-updates, but to remove the need to alter the tag.