[meta] 4.0.0 release roadmap

Hello Dan!

Few hours before Your comment I posted an alpha release :)
I'll try to find some time to update all issues as soon as possible.
Also I suppose we will need a new roadmap after few feedbacks.

Regards Olga.

I just released alpha3. Now that all of those RTBCs are out of the way, we can start taking a look at what else is left.

If anyone wants to take on #2925924: Get tests working again, I'd really appreciate the help!

Would be nice if we could get #2867713: Support for "has value" input on all core field widgets done before a beta, but I don't see too much interest in it, so maybe for stable.

alpha5 is now out.

Moved some items from Beta to Alpha, and added #3068112: The tests are deprecated and some conditionals are not working. to Alpha.

Added #3077803: Make ConditionalFieldsFormHelper class instantiable to the alpha list as it's a follow-up to #2926132: OOify contents of conditional_fields.api.inc and then delete it.

I just released an alpha6.

Re-saving to update issue states.

@colan: Awesome work! 1+ and heads up for this. (Thanks for letting me know that I mixed up my browser tabs. :) ... )

Review: I have tested the project latest version alpha 6 and would strongly recommend to release the first beta based on v. alpha 6 to encourage further development. The project works much better than some other beta projects and it needs some more attention and reviews. Call for other users to please report back to move on from "needs review" to a final release...

#18: Thanks for the encouragement, and your testing is greatly appreciated!

However, the couple of remaining issues (there are only two) are or could be API-breaking changes, which should be resolved before we get to beta. Once those are in I'd be happy to cut a beta release.

If you could help with those, or can encourage others to help, that would certainly speed things along.

Sure! Makes sense to me. Are they tagged or do you have quick links? Maybe we can chime in with patches?

See the list above. :) Yes, please provide patches. One person grabbed one of them, but there's no evidence he's actually working on it. So feel free to take over.

Just found another one, sorry!

@colan: sorry for being off-track from this the last 3 months. And thanks for your helpful replies. Sometimes the tired eye is blind :-) I try to get back on it over holidays now.

Added #3134183: Functional JavaScript tests are failing.

Added #3143380: [Plan] Prepare conditional_fields to security advisory coverage applications to the list of stable items.

(Resaving to update issue states)

Hi!
Can we add this issue to the roadmap? #3207751: URL validation of link field doesn't work

Sure, just add above.

Adding #3207751: URL validation of link field doesn't work to alpha release.

Hey there! Sorry for bothering..
Is there any chance new release will go live within the next month or two?
Thanks in advance for your answer!

Apologies if this question is out of scope -- if it is, lmk and I'll post a new issue!

Maintainers: Do you have reason to believe Conditional Fields will be covered by the security policy when there's a stable release, or no, or not necessarily, or?

Thank you!

I just enabled it. So yes.

Well that's pretty fabulous, thank you @colan!

Updating the search for Paragraphs-tagged issues under "Beta"-section, since there's only one issue.

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 #3423942: Enable testing with GitLab CI to the roadmap for a beta release.

Weekend report: Maybe I was on steroids or in "Ninja Turtle / Yoda" mode or something? I dunno...

Reviewed / Responded / Fixed / Closed / Commented / Committed / Cleaned up all together all over 100~200 issues including 10 RTBC's over this weekend. (With about maybe less than 2 or 3 hours sleep the last two days. I def. should keep these new coffee beans...)

So: First Drupal 10 ready BETA release is around the corner!

... (And I have inflammations in the eyes, shoulder and hand now, and my laptop smokes...)

@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 #3105263: Support for Layout Builder to BETA 2, which is at least as important as paragraphs support, if not even more (core).

Added #3377983: Comparison of WYSIWYG field values fail because of HTML tags involved to the stable required tasks.

Added #3344587: Support for field hidden by condition losing its required status 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

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?

• #3207751: URL validation of link field doesn't work
• #2859667: Conditional Required Field not Evaluating on Save with Autocomplete widget
• #3105263
• #3344587: Support for field hidden by condition losing its required status
• #3377983: Comparison of WYSIWYG field values fail because of HTML tags involved

Could we add the following to one of the lists?
#3507266: Empty action sets field value to "undefined"

It looks like from the issue summary you could move to beta release for sure. Thanks @heddn.

@jcandan It's got an RTBC! Would probably be good to move all outstanding issues to MRs.