[meta] 4.0.0 release roadmap

I notice two hings:

1. There are 4 RBC issues for the 4.x branch, one of which was last updated in 2022.
2. The issue summary lists just 3 issues that need to be fixed before releasing a beta version. From the comments, one or two of those may be ready to be closed as outdated.

Maintainers: what can I do to help move this module towards a beta and full release? Would you like me to re-review the RTBC issues? Would you like me to work on the issues listed in the issue summary? Would you like a new issue to enable testing with GitLab CI?

I could make you a co-maintainer so you could do all of that and more (e.g. cut releases). What do you think?

@colan:

I am willing to be added as a maintainer (or co-maintainer).

The project page mentions the #conditional_fields Slack channel and describes @diqidoq and @heddn as the active maintainers. Is that still accurate?

It could be. I have no idea as I'm out of the loop. Maybe reach out to them? I'll leave it to you to sort that out. :)

Anyway, congrats; you're on the maintainer list! Good luck and thanks.

@colan:

Thanks. I will ping @diqidoq and @heddn and try to coordinate with them. Either way, I will see if we can make some progress towards a full release.

I am also adding 📌 Enable testing with GitLab CI Active to the roadmap for a beta release.

@benjifisher: As I sad already on Slack: welcome on board! +1 Glad to get more helping hands here. And thanks @colan (as always) for being responsive and bringing things together quick. :)

Maintainers: what can I do to help move this module towards a beta and full release?

@benjifisher: Gitlab testing is an important addition now and I am sure we all appreciate your work on this! I would even say it has a certain priority to go on with upcoming issues and work on CF. +1 for your interest in it and as I saw you already worked on it. Very much appreciated. Thanks!

• There are 4 RBC issues for the 4.x branch, one of which was last updated in 2022.
• The issue summary lists just 3 issues that need to be fixed before releasing a beta version. From the comments, one or two of those may be ready to be closed as outdated.

No need. All done already. See my comment above. Have cleaned up the issue queue off from 100~200 issues incl. many outdated 12 year old cadavers this weekend... with some very interesting findings :) and incl. 4 newer and 8 very old RTBC issues (reviewed, commented, committed, etc.) with a EOL comment on the old ones regarding upcoming EOL of Drupal 7. But who knows maybe somebody still need these fixes, so I reviewed and committed them too.

The intension for this issue clean-up was that I was actually close before to plan/coordinate a first BETA release with @colan and @heddn very next time soon and I was about getting in touch with both for it. And in that moment you came around. :) Which is great!
+1 Feel free to contact me anytime on Slack in the conditional_fields channel that I have created (EDIT: you already did). I am quite responsive, at least, if I find back into another thread later, which popped up on my mobile, hah. :)

One nit-pik here on the roadmap if you don't mind: I am not sure if we need to hold back a first BETA1 release by Gitlab CI testing support. Releases are for the users and for the public and Gitlab testing is for issue reporters, contributors and maintainers. So I see no problem in releasing beta1 before this is in for beta2. It will be most important in the 4.x dev branch anyways. Awesome and needed addition by the way! Changed the summary accordingly.

Welcome! Glad to have you with us!

Added 🐛 Comparison of WYSIWYG field values fail because of HTML tags involved Needs review to the stable required tasks.

Added 📌 Support field turning hidden by condition to loose its required status Needs work to the Beta2 release task group.

I'm not sure if this is the right way to post here, but I would like to be added as (co-)administrator. I would like to help keep the Conditional Fields up to date for Drupal versions 11 and 12 ect

dqd → closed merge request !56

I'm not sure if this is the right way to post here, but I would like to be added as (co-)administrator.

Thanks for willing to help and contribute to Drupal and the contrib area. Every contributor is very welcome. But before you can enter roles like co-maintaining a module on Drupal.org you should get more involved with the community and should be more active in the community spots here and there so that people can get a better understanding of who you are, etc. Also: Please read the community guidelines and how-to's before starting to contribute to Drupal projects. This will help you to focus on the important parts without frustration by taking actions which lead to unwanted reactions. Hope it helps!

The meta issue is for collecting to-do's and tasks for an upcoming release.

Hello, thank you for the message. I will look into this.

@dqd @heddn could you create alpha6 release with D11 support?

Alpha6 → release provided. There are only a few issues left to get us to a fully stable release. Are all of these still important to reach that goal or with the passage of time do some of these seem less important?

• 🐛 URL validation of link field doesn't work Fixed
• 🐛 Conditional Required Fields not Evaluating Needs work
• #3105263
• 📌 Support field turning hidden by condition to loose its required status Needs work
• 🐛 Comparison of WYSIWYG field values fail because of HTML tags involved Needs review