WordPress.org

Make WordPress Core

Opened 2 years ago

Last modified 3 months ago

#19737 new defect (bug)

"What's New" screen confusing for minor updates

Reported by: scribu Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 3.3
Component: Help/About Keywords: ux-feedback
Focuses: ui Cc:

Description

As reported on WPTavern, when you ugprade to 3.3.1, the "What's New" screen makes it seem like all the new features were introduced in 3.3.1 and not 3.3.

We should add a header below the short summary to the effect of "New features introduced in 3.3".

Change History (8)

comment:1 follow-up: nacin2 years ago

  • Keywords ux-feedback ui-feedback added
  • Milestone changed from 3.4 to Awaiting Review

This was widely discussed on tickets and in IRC. It was decided that a maintenance/security release was just another "feature" and should have similar styling. I can see how it can be confusing, and there were some arguments made that an in-branch update should behave differently than an update that crosses a major version, but nothing came of it.

comment:2 in reply to: ↑ 1 chipbennett2 years ago

  • Cc chip@… added

Replying to nacin:

...an in-branch update should behave differently than an update that crosses a major version, but nothing came of it.

Yes, this exactly. My recommendation would be only to show the "Welcome" screen when the version change is major - i.e. 3.2.x to 3.3.x. Presumably, an install undergoing a version change from 3.3.x to 3.3.y would already have shown the "Welcome" screen upon update to 3.3.x, so there would be no need to show it again.

As a compromise, perhaps add a one-time admin notice upon minor-version update, with a note/link directing the user to the "Welcome" screen in order to see the version changes.

At the same time, regardless of the eventual approach taken, adding the minor-version changes/updates to the "Welcome" screen would still be useful/beneficial, since the screen still exists even if not displayed by default upon update.

comment:3 nacin2 years ago

As we're trying to de-emphasize the importance of point release updates (not as in "you don't need to update" but rather "no big deal" and "might as well be automatic") we should probably not redirect to the welcome screen the same way we do for a major release.

comment:4 chipbennett2 years ago

Possibly related: #19762

comment:5 DrewAPicture15 months ago

  • Component changed from UI to Help/About
  • Keywords ui-focus added; ui-feedback removed

comment:6 follow-up: celloexpressions3 months ago

Now that minor updates are automatically installed for most sites, is this still much of an issue? It might be worth skipping the about page, but I'm not sure that that's needed anymore since most users won't manually update to a minor release anyway.

comment:7 in reply to: ↑ 6 nacin3 months ago

Replying to celloexpressions:

Now that minor updates are automatically installed for most sites, is this still much of an issue? It might be worth skipping the about page, but I'm not sure that that's needed anymore since most users won't manually update to a minor release anyway.

This is very true. Most simply won't see this page. As I said two years ago, above:

there were some arguments made that an in-branch update should behave differently than an update that crosses a major version, but nothing came of it.

I guess something came of it. :-D

comment:8 nacin3 months ago

I think one thing that could make it a little more clear is saying "What's new in 3.8" versus "3.8.1". But the Z in X.Y.Z is due for a de-emphasis across the entire admin.

(And then eventually we can de-emphasize the second number, and then the first...)

Note: See TracTickets for help on using tickets.