- 🇳🇿New Zealand quietone New Zealand
There have been no further comments for a year, so am I closing this as catch suggested in #20.
Automatically closed - issue fixed for 2 weeks with no activity.
Despite our efforts, we keep introducing regressions with every minor release. This is problematic for many (obvious) reasons:
On top of that, regressions in minor upgrades don't only affect complex websites, that are likely to have developers taking care of them, in fact they hit harder one of the audiences Drupal has been historically good at serving: moderately complex websites with low budget and lack or scarcity of technical expertise. Some of the 8.6.0 update issues → were even reported by sites with very simple setups.
And again these regressions happen despite our best efforts. Some update issues can be caught on review or via automated tests, although the most complex updates are normally part of big patches, so it’s easy for problems to go unnoticed → . On the other hand some bugs are hard or nearly impossible to catch by simply writing a regular automatic test: #2997982: Orphan term hierarchy records can cause taxonomy_update_8502 to enter an infinite loop → is a glaring example.
Last but not least, automatic updates → are going to exacerbate these issues, if we don't take action.
Significantly widen the tested scenarios.
This could be accomplished in many ways, that aren’t mutually exclusive:
This idea aims to prevent regressions and is related to 🌱 Create an official "Minor release upgrade path" initiative Closed: outdated that instead focuses on dealing with existing regressions in a better way.
Fixed
Proposed Plan
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
There have been no further comments for a year, so am I closing this as catch suggested in #20.
Automatically closed - issue fixed for 2 weeks with no activity.