-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plan for WDL 1.2 support? #703
Comments
Yes, here is the plan to make a plan. Right now I've been focusing on some "meta" technical debt, especially #668. That's going to be equally important to keeping the project healthy in the long term. Then I will make a thorough pass through the new spec and file tickets, then start burning them down, where any contributions would certainly be welcome. Best guess, I'd hope to ship it all towards the end of Q3. As you note, I think the most complex of the new features are already done ( |
Thank you and truly appreciate the details and timeline. This is exciting! Close here as this is just a question. Still happy to help if feasible. |
Hey @mlin i just wanted to come back to this and see what support you need from the community to get 1.2 over the line. I think there are a number of us that would be happy to contribute some time if we know the checklist |
I am also very curious for your plans on this, @mlin. |
First, thank you for the great engine and tools here! We have been benefiting from your hard work here for a while 🙏
Second, I've tried searching code, PR, issues, projects and didn't fine much info so could have missed; apologize if so.
It seems WDL 1.2 has been nailed and released for a month or so. I hope it's not too early to ask but is there a plan/roadmap for miniwdl to start supporting WDL 1.2? Technically, miniwdl support
development
which is hopefully closer to 1.2 than 1.0. But I know the devil is in the detail so just want to kindly ask for plan rather than results 😄 (Just in case this helps in any way, happy to contribute though I doubt how much I can be useful 😅 ).The text was updated successfully, but these errors were encountered: