WordPress.org

Making WordPress.org

Opened 7 years ago

Last modified 10 months ago

#45 new task

Theme repository - add changelog listing tab

Reported by: mario-siteground Owned by:
Milestone: Priority: normal
Component: Theme Directory Keywords:
Cc:

Description

Listing the changelogs for WordPress themes on http://wordpress.org/themes would be helpful for people to revise theme progress while updating.

Submitted in detail as 22810 on Core Trac

Attachments (2)

Twenty Seventeen WordPress org-4911.jpg (208.7 KB) - added by joyously 2 years ago.
what the theme directory looks like
bbPress WordPress org-4932.jpg (217.6 KB) - added by joyously 2 years ago.
what the plugin directory looks like

Download all attachments as: .zip

Change History (14)

#1 @Daedalon
7 years ago

Pending on Theme Review Team to agree on the format. According to 22810 on Core Trac this may not have yet been brought to their attention and I don't see a way to do that without subscribing to a mailing list that would notify us of discussions we're not interested in following.

#2 @jcastaneda
7 years ago

  • Cc jomcastaneda@… added

#3 @ericlewis
6 years ago

  • Priority changed from low to normal

Seconded - admins will browse changelogs for themes when upgrading. We should surface this information.

#4 @jcastaneda
6 years ago

We should surface this information.

Yes, very much needed and looking forward to making this happen. Though because the theme repo was recently redesigned, would this need to be modified? A link below or above the last updated section could be one way to expose it I would think.

Discussion began: https://make.wordpress.org/themes/2015/04/26/changelog-proposal/

First iteration: https://make.wordpress.org/themes/2015/04/29/a-revised-readme/

This ticket was mentioned in Slack in #themereview by jcastaneda. View the logs.


5 years ago

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


3 years ago

This ticket was mentioned in Slack in #themereview by jcastaneda. View the logs.


3 years ago

#8 @joyously
3 years ago

For reference, here are current screenshots of a theme page and a plugin page.

(Sorry that the image links are no longer available. I attached new ones.)

Last edited 2 years ago by joyously (previous) (diff)

@joyously
2 years ago

what the theme directory looks like

@joyously
2 years ago

what the plugin directory looks like

#10 @dingo_d
10 months ago

We agreed on a triage meeting that the following things need to happen in order for people to start contributing

  1. Ask somebody from meta to provide the data for twenty themes
  2. Help with setting up meta environment and injecting the data from 1. into relevant databases
  3. Work on issues

This way we can actually start applying patches for this.

The fix for the current issue is not problematic:

We need to store changelog data from the readme (if it exists) in the meta during the get_readme_data() run of the upload, then just see how to reuse this information on the themes page.

#11 follow-up: @joyously
10 months ago

We need to store changelog data from the readme (if it exists) in the meta during the get_readme_data() run of the upload, then just see how to reuse this information on the themes page.

If we add the code to store the new data, how do we populate all the data for existing themes?
Or does it matter?

#12 in reply to: ↑ 11 @dd32
10 months ago

Replying to joyously:

We need to store changelog data from the readme (if it exists) in the meta during the get_readme_data() run of the upload, then just see how to reuse this information on the themes page.

If we add the code to store the new data, how do we populate all the data for existing themes?
Or does it matter?

I wouldn't worry about that too much - I assume someone on the dotorg side of things could trigger re-imports for the last few hundred themes, but in general importing changelogs for themes not currently being updated would provide very little benefit IMHO.

Unless someone felt comfortable doing it, I've always said "Make it work from now on, that's the safest and most straight forward option"

Note: See TracTickets for help on using tickets.