Thanks for your message. Generally, I spend at least a couple hours a week reviewing the PRs, sorting through the incoming issues, and responding on mailing lists. My other teammates do the same thing, but I'm the main point of contact. When I'm away on vacation, you'll be seeing longer delays than usual.
In general, you're welcome to ping the mailing list, kritis-users, with proposal to include the PR in the next minor (feature) or micro (bug fix) release, to see if anyone else wants to either add to it or has a different perspective. I get notifications for all PRs and GH issues being sent, so it's just a matter of when in the week I'm able to get to them, but you're always welcome to reach out directly to me or to whomever is assigned as the reviewer on the PR. Always open to feedback on how to improve this process!
Cheers,
Aysylu
Hi Aysylu,
Sorry for my abrupt message but I didn't know what was the best way to communicate with you.
I would like to know what can we expect regarding a recent PR we send to the Kritis project. I don't know how much time you guys have for review and how long should we expect the code to be merged if accepted, then when is released or officially images build. Should we consider this is not going to be in until 0.2? Depending on that we will organise internally and plan our time accordingly.
Let me know what is your preferred way to being contacted(if any) or what is the common timing for handling these issues/PRs.
Thanks and I look forward to hearing from you.
--
Diego Comas
Tech Lead Manager, Thought Machine
Data Classification: Private
Thought Machine Group a limited company registered in England & Wales.
Registered number: 11114277.
The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.