![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 9 years ago
Closed 9 years ago
#42103 closed defect (bug) (duplicate)
Impose an changelog when submitting an update
| Reported by: | Djibs13 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | WordPress.org Site | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
Many plugins are updated without adding a list of changes or new features. It is very important for users to know what changes when they will update the plugin.
Sometimes it takes several days before an changelog apapraises on the plugin page; sometimes it is several weeks.
Changelog should be imposed at the time of submission. It should have been done for a long time.
This also applies to the Wordpress team. For example, the WP-Super Cache Plugin has been updated to version 1.5.6 and still no changelog after more than 24 hours on the plugin page.
Attachments (1)
Change History (4)
#2
@
9 years ago
- Keywords close removed
@danieltj That's not the problem. The problem is the version in the iframe seems to be heavily cached.
#3
@
9 years ago
- Component Plugins → WordPress.org site
- Milestone Awaiting Review
- Resolution → duplicate
- Status new → closed
This is already tracked in https://meta.trac.wordpress.org/ticket/3107.
Sometimes it just takes time for the plugin directory to show the latest updated changelog. I don't think I've seen a plugin not updating it's readme.txt with a change log. If for whatever reason a change log isn't included or updated the plugin author might just need a nudge so they can make/update it is all.