Hello,
A new project I'm on is planning out their D11 release and this is one of the modules needing one. The client is particular and may push back on switching to another scheduler module so would like to get this one a full release
I would probably continue on the 2.0.x branch and make it just 10.3/11 so we can do some more modern php stuff and core stuff.
Would also triaging the queue, lot of overlapping stuff that a gitlab file would fine, some credit farming tickets, etc.
Currently maintain/co-maintain 50+ modules and a few sub-components on core
Let me know what you think!
Active
2.0
Code
So I originally put in the request for a client project. But they've since said we can swap out the scheduler option with something like scheduled_transitions or scheduler. So not sure how much time I'll have for this, any objection to marking it obsolete?
Automatically closed - issue fixed for 2 weeks with no activity.