One of the saddest UX failures of Drupal (and now Backdrop) is when someone updates field display settings four or five times with no effect. Usually this is because they click the "Update" button thinking their settings will update, but they don't. Not unless they also hit "Save". And the "Save" button is usually below the fold, so the poor unsuspecting user may not even know there is a save button.
Secret save
To solve this problem, we should make the update button actually save, too.
Related issue: https://github.com/backdrop/backdrop-issues/issues/573
Recent comments
I'm glad you've found it quite useful too! I'm curious to know why you'd like to unpublish some of your modules or themes? They're not ready or are they more personal projects? I can help...
My work and a big thanks to all of you
Slight improvement to @argiepiano's procedure. Again for PR 4690, it would be: Using shell access, go to the Backdrop doc root. Run this command to get the diff file...
Workflow for core update with fixes that are not yet in core
This issue is seeing some progress, but there are some questions that might benefit from a UX discussion. https://github.com/backdrop/backdrop-issues/issues/2894
Apr 18th Weekly Meetings