- Issue created by @cilefen
- 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
Thanks, @cilefen. Given how close Drupal 11 is, I was thinking perhaps we should make 6.3.x to be the same as 6.2.x except compatible with Drupal 11 and do feature development on 6.4.x. Thoughts about branching strategy?
- 🇺🇸United States jrockowitz Brooklyn, NY
Let's hold off creating 2 new branches. Maybe we can fix D11 deprecation issues in 6.2.x.
- 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
OK, that makes sense. 6.2.x will be only for bug fixes and Drupal 11 compatibility. Changes made there are merged into 6.3.x, which will be for feature development.
I think we should pause for a couple of weeks before creating the branch since there may be issues arising from the 6.2.0 release and Drupal 10 upgrades.
- Status changed to Fixed
28 days ago 7:42pm 23 November 2024 - 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
At this point, I think any feature development should be against 6.4.x (or just 6.x) so that 6.3.x can be a stable branch for Drupal 11 compatibility with the current feature set.
- 🇺🇸United States jrockowitz Brooklyn, NY
I am open to 6.3.x having some minor features/improvements that are backwards compatible.
Automatically closed - issue fixed for 2 weeks with no activity.