Problem/Motivation

Meta issue to ensure compatibility with Drupal 9 only.

@see Child issues (in the right sidebar)

Comments

paulocs created an issue. See original summary.

paulocs’s picture

paulocs
Primary language Portuguese, Brazil
Location Belo Horizonte
commented
Issue summary: View changes
jrockowitz’s picture

jrockowitz commented
Issue summary: View changes

Adding a bunch on 9.x related tickets. Once we have a full list, each one of the tickets listed should be updated to include this ticket as the 'Parent issue'.

jrockowitz’s picture

jrockowitz commented

I am not ready to move to only support 9.x because the usage stats indicate that a lot of sites are still on Drupal 8.x.

When supports Drupal 8.x becomes a blocker for moving things forward, we should drop Drupal 8.x support.

jrockowitz’s picture

jrockowitz commented

So I think the next steps are to...

  • Start switching all the related issues to RTBC.
  • Do one more 6.1x. release
  • Create a 6.2.x branch
  • Commit all the Drupal 9.x issues to the 6.2.x branch
  • Tag a 6.2.x beta
  • Move 6.0.x to unsupported

My thoughts on moving forward are...

Because 6.2.x is more of a cleanup/compatibility branch for the time being. Most PRs will be merged in 6.1.x and then 6.1.x will be merged in 6.2.x. 6.x will be in sync with 6.2.x.

Ideally, in June 2022 we can stop supporting Drupal 8.x only focus on 6.2.x.

I will document the status of each branch/release via the Webform module's project page once I create the 6.2.x branch.

Does this make sense?

jrockowitz’s picture

jrockowitz commented
Issue summary: View changes
jrockowitz’s picture

jrockowitz commented
Status: Active » Fixed
jrockowitz’s picture

jrockowitz commented
Version: 6.x-dev » 6.2.x-dev
Status: Fixed » Active
jrockowitz’s picture

jrockowitz commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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