Problem/Motivation
- Update composer.json for Drupal
9.1.x
| Comment | File | Size | Author |
|---|---|---|---|
| #68 | 3186209-68-3.x.patch | 5.99 KB | yas |
| #58 | 3186209-58-4.x.patch | 2.63 KB | yas |
Issue fork cloud-3186209
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3186209-update-composer.json-for-drupal-9.2.x
changes, plain diff MR !252
Comments
Comment #2
yasLet me try.
Comment #3
yasComment #4
yasComment #5
yasComment #6
yasComment #7
yasComment #8
yasComment #9
yasComment #10
yasComment #11
yasComment #12
yasComment #13
yasComment #14
yasComment #15
yasComment #16
yasComment #17
yasComment #18
yasComment #19
yasComment #20
yasComment #22
yasComment #23
yasComment #25
yasComment #27
yasComment #29
yasFixing the coding standard violations.
Comment #30
yasComment #31
xiaohua guan commented@yas
The patch looks good to me.
Comment #32
baldwinlouie commented@yas, I have a question about the patch.
Does this mean cloud module will only support Drupal 9+?
Comment #33
yas@xiaohua-guan @baldwinlouie
Thank you for your review.
Yes, that's a very good point. When we want to upgrade
"maclof/kubernetes-client": "~0.17",(0.17 or higher), it is not compatible with Drupal8.9.x. Here is the error:D9+ looks compatible with those symfony libraries. Therefore if we upgrade
maclof/kubernetes-client, we need to drop Drupal8.xAt this point, this
composer.jsonis our golden combination to support Drupal9.1.xor higher.However... on my second thoughts, we should apply this patch to
4.xto be created when we release3.0.0. What do you think?PS I refactored the patch.
Comment #35
yasComment #36
yasComment #38
yas@baldwinlouie @xiaohua-guan
Suddenly the tests started to fail; looks due to the problem in Drupal Core: PHPUnit 9.5 Call to undefined method ::getAnnotations()
Comment #39
baldwinlouie commented@yas, thank you for the explanation. I was thinking how best to support Drupal 8 and Drupal 9. When I read this: https://www.drupal.org/docs/understanding-drupal/drupal-9-release-date-a..., it states Drupal 8 will be supported until November 2, 2021. But importantly, it states only patches and security releases will make it into Drupal 8. No new features.
For our module, I like your idea of dropping Drupal 8 support in the 4.x branch. I think it is a bit sudden to drop Drupal 8 support right before a stable 3.x release.
That way, it is a clean break when we start working on 4.x
Comment #40
yas@baldwinlouie
Thank you for your comment and the link. Let's keep supporting Drupal 8 and drop it in the
4.xbranch.They fixed the issue quickly, so this patch should be ready. Let's keep
RTBCstatus w/o merging this patch until we start to develop4.xbranch.Comment #41
yasUpdated the patch for the recent merges.
Comment #43
yasComment #44
yasUpdated the patch.
Comment #46
yasComment #47
yasRemoving
AwsCloudServerTemplatePluginandK8sCloudServerTemplatePluginfixes since those fixes are included in the patch at #3190294Comment #49
yasComment #50
yasComment #51
ilgnerfagundes commentedI applied patch # 47 it applies correctly. For me everything is correct, rtbc +1
Comment #52
yas@ilgnerfagundes
Thank you for your help. As I mentioned in #3195065, we have our upgrade plan. We will include this patch into our
drupal/cloud:4.x branchwhen we create it soon.Comment #54
yas@all
Updated the patch due to the merge at #3218796: Update composer.json to release 3.0.0
Comment #55
yas.
Comment #56
yasComment #57
yasUpdating the patch file. Thanks to @xiaohua-guan, we are fixing the issue on Drupal
9.2.x.Comment #58
yasAdding a patch for the
4.xbranchComment #59
yas@xiaohua-guan @baldwinlouie
The tests have been passed successfully on Drupal 9.2.x, so I'll merge the patch at #3186209-58: Update composer.json for Drupal 9.2.x to
4.xand close this issue asFixed.Comment #62
yasComment #64
yasRe-opening this issue since we need to apply the patch.
Comment #65
yasComment #66
yasComment #67
yas@all
The tests have been passed successfully, so I'll merge the patch to
3.x, and close this issue as Fixed.Comment #68
yasComment #70
yas