@jhodgdon, thank you for all your work maintaining config update. Would it be possible to tag a 8.x-1.7 release that would include the following fixed issues? Also, are there any other open 8.x issues that should be included in 8.x-1.7? (i.e. #3054659: Invalid parameter for report URL if module config file is malformed)

Comments

Chris Matthews created an issue. See original summary.

chris matthews’s picture

chris matthews commented
Issue summary: View changes
jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Related issues: +#3089420: Make sure Config Update Manager is Drupal 9 compatible, +#3042621: Refactor to not support Drush 8 any more, +#3056249: Default config hash is not generated for imported configuration, +#3043561: Report not ordered alphabetically

There are several other open bug issues that would be nice to get fixed, and they are in progress.

Also I don't think these should have been made "child" issues. Related would have been nicer. No worries though! At least they are shown in the sidebar.

chris matthews’s picture

chris matthews commented

Thanks jhodgdon, I've seen maintainers do it different ways (child, related, only in the IS) but glad it works ok.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Yeah it's definitely personal preference! All works.

Personally, I only use Child issues for a set of related issues that solve an overarching problem. I wouldn't use it for "put these into the next release" because the issues are not really related to each other or to this issue except by timeframe.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Status: Active » Fixed

Release created today.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.