This is a summary of the shiny updates chat from May 3. (Slack log)
Attendees: @ocean90, @swissspidy, @ethitter, @adamsilverstein, @mapk, @obenland
- Accomplished work since last week
- Remaining work
@obenland will work on the Shiny Updates landing page for feature projects and fix a bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. that were discovered during the most recent user test. @mapk offered to conduct another user test focused on the new interactions with some learnings from the previous one. Goal is to identify any hiccups or behaviors that are unexpected to users. @swissspidy wants to continue working on
update-core.php and see if we can get it into shape for 4.6.
- Most recent user tests
We briefly talked about the most recent user test (linked above). It showed a variety of bugs that @obenland initially assumed were based on being in subviews of the plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party list. After the meeting it turned out that the test site ran an outdated version of WordPress that didn’t include some of the date that Shiny Update needs to work. It was a good demonstration of progressive enhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. here though, as all actions still worked, they just weren’t shiny. More user tests to come, to make sure that users agree with the new interactions.
- Schedule for 4.6 inclusion
Next up is writing the merge proposal that was requested to be published around 6/1, definitely before 6/8.
Next meeting is on Tuesday May 10, 19:00 UTC.