-
Notifications
You must be signed in to change notification settings - Fork 72
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
******** General Announcement ******** #723
Comments
Welcome @carl-hostrander! A big thumbs-up from me regarding the proposed release cycle of June and October. |
Thanks @carl-hostrander - great to see a focus on a clean up! - feel free to reach out if there's anything I can help with! :-) |
Welcom @carl-hostrander. |
Hi @carl-hostrander. It looks like there has been a lot of great work going on here in the git repository. I was just wondering if you have any plans for when there might be another release of the plugin to the Moodle plugins database? Thanks. (And, is it OK for me to use this issue to ask this question? Sorry if this was out-of-order.) |
@timhunt - Hi! We are planning on another round of releases for all of our plugins towards the end of October. These release will fix various issues and introduce support for version 4.5 |
Thanks :-) |
Hello community!
I am Carl and would like to announce that I am the tech lead overseeing the Turnitin Moodle Plugins. My goal is to address the issues and submitted pull requests in a timely manner when they are submitted. We are planning to have plugin releases twice a year, in June and in October where needed.
Unfortunately, I have inherited a lot of unresolved pull requests and issues. The action plan for resolving these will be to work from the latest to the oldest. There is a caveat to the term oldest. Currently we support versions 4.1+ up to and including 4.4+. Moodle 4.1 originally was release in November, 2022. Any issue that has been tagged with version before that will have a comment and then closed. If the issue is still pertinent to you, please retest in supported version of Moodle and either create a new issue or comment on the current issue, denoting version tested on and re-open the ticket. The reasoning behind this is that fixes have gone out that may have already resolved the issue or a fix has been implemented but the issue has not been closed in repo. Also, I don't have the resources right now to investigate every single issue that is not pertinent to a supported release.
Lastly, I would like to say, if you believe an issue or pull request needs immediate action please tag me to let me know. Also, here are a few notes on this repo:
The text was updated successfully, but these errors were encountered: