Re: Stepping down from Patch Meister role
Le 30/01/2022 à 22:07, Jean Abou Samra a écrit : Le 30/01/2022 à 18:19, James a écrit : Documentation and Patch Meister ? OK. But I see that you just deleted your GitLab account. Does this mean you no longer intend to contribute? I was hoping you would stay with us for documentation, bug triage, etc. Of course, if you are moving on, thank you for all of your contributions (so not just patch countdowns), and enjoy what will be next in your life. I only received the countdown email after sending this. I've now opened https://gitlab.com/lilypond/lilypond/-/merge_requests/1171 Meanwhile, I got an email bounce for the apparently deleted address pkx1...@posteo.net. Farewell, James.
Re: Stepping down from Patch Meister role
Le 30/01/2022 à 18:19, James a écrit : Hello, On 29/01/2022 18:00, Jean Abou Samra wrote: Le 28/01/2022 à 10:49, pkx1...@posteo.net a écrit : Why don't you do the 'next' countdown (on Jan 30th) while I am still about and let me know what problems/questions you had or need to understand how to resolve? That way there is at least some percieved semblance of a hand-over. One thought in passing: we need to update the Contributor's Guide as well as http://lilypond.org/authors.html. James, how should you be called on the latter page? Documentation and Patch Meister ? OK. But I see that you just deleted your GitLab account. Does this mean you no longer intend to contribute? I was hoping you would stay with us for documentation, bug triage, etc. Of course, if you are moving on, thank you for all of your contributions (so not just patch countdowns), and enjoy what will be next in your life. All the best, Jean
Re: Stepping down from Patch Meister role
Hello, On 29/01/2022 18:00, Jean Abou Samra wrote: Le 28/01/2022 à 10:49, pkx1...@posteo.net a écrit : Why don't you do the 'next' countdown (on Jan 30th) while I am still about and let me know what problems/questions you had or need to understand how to resolve? That way there is at least some percieved semblance of a hand-over. One thought in passing: we need to update the Contributor's Guide as well as http://lilypond.org/authors.html. James, how should you be called on the latter page? Documentation and Patch Meister ? -- Regards James
Re: Stepping down from Patch Meister role
Le 28/01/2022 à 10:49, pkx1...@posteo.net a écrit : Why don't you do the 'next' countdown (on Jan 30th) while I am still about and let me know what problems/questions you had or need to understand how to resolve? That way there is at least some percieved semblance of a hand-over. One thought in passing: we need to update the Contributor's Guide as well as http://lilypond.org/authors.html. James, how should you be called on the latter page? Regards, Jean
Re: Stepping down from Patch Meister role
Le 08/01/2022 à 12:15, Jonas Hahnfeld via Discussions on LilyPond development a écrit : Am Samstag, dem 08.01.2022 um 10:06 + schrieb James: Hello, I am going to stop doing the Patch countdown at the end of this month. I'll continue for the next few weeks, but my last countdown will be whatever the last date in January ends up being. Thanks for your understanding. Hi James, Thanks a lot for all you did for helping Lily's development. Enjoy your new life! Cheers, -- Jean-Charles
Re: Stepping down from Patch Meister role
On 2022-01-28 02:49, pkx1...@posteo.net wrote: Colin, Why don't you do the 'next' countdown (on Jan 30th) while I am still about and let me know what problems/questions you had or need to understand how to resolve? That way there is at least some percieved semblance of a hand-over. You may want to do things differently but my starting point (and bookmark) for any countdown is https://gitlab.com/lilypond/lilypond/-/labels An excellent thought, James, received with thanks! Cheers, Colin
Re: Stepping down from Patch Meister role
Colin, On 28/01/2022 09:13, Jonas Hahnfeld wrote: Am Mittwoch, dem 26.01.2022 um 15:57 -0700 schrieb Colin Campbell: On 2022-01-26 14:29, pkx1...@posteo.net wrote: Hello Colin, Good morning to you,James! A couple of quick(ish) questions: Given a gitlab account, based on this email, do I need formal permissions within Lilypond? Yes, IIRC Jonas will need to give you a level of access so you can comment and change labels of MRs (i.e. move MRs from Patch::review to Patch::push etc). Excellent, James; just what I needed. As this is copied to the devel list, I'm hoping it will serve as my request to Jonas, per the CG. Done [1]. (Sorry for the slow response from my side, too much going on around me right now.) I'm very happy that we've found a volunteer to "take on the job". If you have any problems with the script or the GitLab interface, feel free to contact me either on- or off-list. I'm happy to help as best as I can. Why don't you do the 'next' countdown (on Jan 30th) while I am still about and let me know what problems/questions you had or need to understand how to resolve? That way there is at least some percieved semblance of a hand-over. You may want to do things differently but my starting point (and bookmark) for any countdown is https://gitlab.com/lilypond/lilypond/-/labels regards James
Re: Stepping down from Patch Meister role
Am Mittwoch, dem 26.01.2022 um 15:57 -0700 schrieb Colin Campbell: > On 2022-01-26 14:29, pkx1...@posteo.net wrote: > > Hello Colin, > > > Good morning to you,James! > > > > > > A couple of quick(ish) questions: > > > > > > Given a gitlab account, based on this email, do I need formal > > > permissions within Lilypond? > > Yes, IIRC Jonas will need to give you a level of access so you can > > comment and change labels of MRs (i.e. move MRs from Patch::review to > > Patch::push etc). > > > > > > Does "middle green tick" refer to what I see on lilypond/merge > > > requests/!? > > > > Yes, if you hover over the middle tick it says 'tests passed'. Click > > it and you get taken to a console window where you can see a URL link > > near the end of the build output that, when clicked, takes you to the > > reg test diffs (if there are any). The back button works OK in gitlab > > to take you back to the MR comment section. > > > > I don't bother clicking on the other '2 ticks' (build and doc) but if > > for example the first two pass and the third (documentation) fail then > > I don't bother even looking at the reg tests as all builds need three > > green ticks to progress as a bare minimum. > > > Excellent, James; just what I needed. As this is copied to the devel > list, I'm hoping it will serve as my request to Jonas, per the CG. Done [1]. (Sorry for the slow response from my side, too much going on around me right now.) I'm very happy that we've found a volunteer to "take on the job". If you have any problems with the script or the GitLab interface, feel free to contact me either on- or off-list. I'm happy to help as best as I can. Cheers Jonas 1: I didn't know that you can invite people based on email, that's actually nice. Maybe we can put this into the CG, which currently only mentions sending the username... signature.asc Description: This is a digitally signed message part
Re: Stepping down from Patch Meister role
On 2022-01-26 14:29, pkx1...@posteo.net wrote: Hello Colin, Good morning to you,James! A couple of quick(ish) questions: Given a gitlab account, based on this email, do I need formal permissions within Lilypond? Yes, IIRC Jonas will need to give you a level of access so you can comment and change labels of MRs (i.e. move MRs from Patch::review to Patch::push etc). Does "middle green tick" refer to what I see on lilypond/merge requests/!? Yes, if you hover over the middle tick it says 'tests passed'. Click it and you get taken to a console window where you can see a URL link near the end of the build output that, when clicked, takes you to the reg test diffs (if there are any). The back button works OK in gitlab to take you back to the MR comment section. I don't bother clicking on the other '2 ticks' (build and doc) but if for example the first two pass and the third (documentation) fail then I don't bother even looking at the reg tests as all builds need three green ticks to progress as a bare minimum. Excellent, James; just what I needed. As this is copied to the devel list, I'm hoping it will serve as my request to Jonas, per the CG. Cheers, Colin
Re: Stepping down from Patch Meister role
Hello Colin, On 26/01/2022 17:26, Colin Campbell wrote: On 2022-01-23 09:15, pkx1...@posteo.net wrote: Colin hi, Apart from the interface of GitLab and a nice countdown script (instead of the old script that was used) it's more or less the same process as before. Different developers, different interface. Patch testing has been completely automated so all you are doing is viewing reg test diffs (middle green tick on the MR, find the link in the cmd window and clikc on it in a browser). All you need is a gitlab login and email. Good morning to you,James! A couple of quick(ish) questions: Given a gitlab account, based on this email, do I need formal permissions within Lilypond? Yes, IIRC Jonas will need to give you a level of access so you can comment and change labels of MRs (i.e. move MRs from Patch::review to Patch::push etc). Does "middle green tick" refer to what I see on lilypond/merge requests/!? Yes, if you hover over the middle tick it says 'tests passed'. Click it and you get taken to a console window where you can see a URL link near the end of the build output that, when clicked, takes you to the reg test diffs (if there are any). The back button works OK in gitlab to take you back to the MR comment section. I don't bother clicking on the other '2 ticks' (build and doc) but if for example the first two pass and the third (documentation) fail then I don't bother even looking at the reg tests as all builds need three green ticks to progress as a bare minimum. Regards James
Re: Stepping down from Patch Meister role
On 2022-01-23 09:15, pkx1...@posteo.net wrote: Colin hi, Apart from the interface of GitLab and a nice countdown script (instead of the old script that was used) it's more or less the same process as before. Different developers, different interface. Patch testing has been completely automated so all you are doing is viewing reg test diffs (middle green tick on the MR, find the link in the cmd window and clikc on it in a browser). All you need is a gitlab login and email. Good morning to you,James! A couple of quick(ish) questions: Given a gitlab account, based on this email, do I need formal permissions within Lilypond? Does "middle green tick" refer to what I see on lilypond/merge requests/!? Cheers, Colin
Re: Stepping down from Patch Meister role
Colin hi,
On 22/01/2022 22:32, Colin Campbell wrote:
On 2022-01-08 03:06, James wrote:
Hello,
I am going to stop doing the Patch countdown at the end of this month.
I'll continue for the next few weeks, but my last countdown will be
whatever the last date in January ends up being.
Thanks for your understanding.
Since James took over from me when I left the fold six years ago,
perhaps I can return the favour now. Fair warning: I left at the start
of what seems to have been a period of significant change, so I'm
rather out of touch with current terms ("patch" as I knew it is now
"merge request"?). With some coaching, and lashings of patience from
the devs, I'm willing to take it on.
Apart from the interface of GitLab and a nice countdown script (instead
of the old script that was used) it's more or less the same process as
before. Different developers, different interface. Patch testing has
been completely automated so all you are doing is viewing reg test diffs
(middle green tick on the MR, find the link in the cmd window and clikc
on it in a browser).
All you need is a gitlab login and email.
James
Re: Stepping down from Patch Meister role
Hello, On 22/01/2022 22:12, Carl Sorensen wrote: James, How much time do you spend per week as Patch Meister? I spend about 15-20 mins every 2 days. I don't review code, I just check reg tests (pasting those that are new or changed significantly) I also make sure all threads that are still unresolved are either really unresolved or just not closed (in the latter case I don't close threads myself but will comment to make sure that the relevant parties know there is a thread that looks like it is still TBD). I don't send personal emails but do everything via GitLab so that all can see responses. The original cadence was 4 days but that was when we had far fewer active developers. It has only moved to 2 days because of the regularity of MRs and patches. I sometimes deliberately make the cadence longer if there are many patches in the three queues so that everyone gets a chance. So Log in, look at the MRs in countdown (and change them to push / leave them or move them down, i.e. to review) then I look at MRs in review and move them to countdown (or if there is still ongoig discussion I will leave it there) and finally I look at MRs in 'new' and check reg tests and set them to review. So I start at the top so to speak and work down. (Coutdown/review/new). Pushing everything up one step and out to patch Push. I then use the 'countdown.py' script in the infrastructure repo that generates the list you see in the emails. I add the date of the countdown in the subject of the email and change the 'next countdown date' in the body and then just send the email to dev. My general rule is any patch in review that is less than 24 hours old stays there (i.e. doesn't get moved on). I rely on developers that resubmit patches, depending on where it was in the queue to either set it back to the new/review queue or state in a note why they don;t think it needs to start back at review again. I try to avoid the 'this is trivial we should push this now' comment because after all unless it is something that is affecting release, it's only 48 hours before the next countdown. Some developers tend to be impatient and I just ilke to make sure everyone gets to comment. No comment in a thread is the same as a LGTM. This saves me having to wait for people to approve explicitly every MR. Sometimes I see a thread in a MR that is not going anywhere and no one is replying or making a decision, so I will comment in the thread that something must be done and if after the next countdown nothing has changed I will 'do something' (be it set it to push or set it to needs work) as that usually generates some attention. But some MRs have been known to sit in 'review' for multiple countdowns and even at 'countdown' until it is obvious that something needs to change. I just state why it has not been moved (reference a comment for example) and then teh developer can tell me why I am wrong or why X needs to wait or why Y can be ignored. I always defer to the developers. It's more or less just shuffling papers and checking reg tests with a bit of comment and running the countdown script that I paste into the email. Hope that helps. James If the time requirement is manageable, I could step in. I don't have lots of time to spend on Lilypond (hence my lack of current development work), but I could plan to spend some. Please help me understand the time you spend. Carl On 1/22/22, 11:09 AM, "lilypond-devel on behalf of Jonas Hahnfeld via Discussions on LilyPond development" wrote: Am Donnerstag, dem 13.01.2022 um 22:42 +0100 schrieb David Kastrup: > Kevin Barry writes: > > > Hi James, > > > > This is a big loss; you will be missed. Thank you for all of your hard work. > > > > > I want to stay a > > > developer and that conflicts both time-wise and with respect to > > > impartiality. > > > > Finding a non-developer to fill James's shoes sounds difficult. I > > would volunteer, but I still plan to contribute patches. > > git shortlog --author Lowe > > should be some indication that this is not a conflict of interest as > such. It may end up a conflict of resources. Yes, my initial message wasn't entirely clear, it's of course possible to contribute patches while being "Patch Meister". The "impartiality" aspect is that you should try to apply the same standards to your own submissions as to all other patches. So, there's around one week left until the end of January and this thread has more or less died down, thus last call for volunteers. Jonas
Re: Stepping down from Patch Meister role
Le 22/01/2022 à 23:32, Colin Campbell a écrit :
On 2022-01-08 03:06, James wrote:
Hello,
I am going to stop doing the Patch countdown at the end of this month.
I'll continue for the next few weeks, but my last countdown will be
whatever the last date in January ends up being.
Thanks for your understanding.
Since James took over from me when I left the fold six years ago,
perhaps I can return the favour now. Fair warning: I left at the start
of what seems to have been a period of significant change, so I'm
rather out of touch with current terms ("patch" as I knew it is now
"merge request"?). With some coaching, and lashings of patience from
the devs, I'm willing to take it on.
Awesome!
Yes, there has been quite a bit of change to the
processes used in the project. We are now hosted
on GitLab (instead of SourceForge and Rietveld).
“Merge requests” are here:
https://gitlab.com/lilypond/lilypond/-/merge_requests
You can find issues in the same place.
There is also a Continuous Integration (automated
testing) system that runs make, make check and make doc
on every merge request. This no longer has to be done
manually or by Patchy. The test results are found in
a link at the bottom of every make check run. When a
developer passes on the merge request (whether the author,
the Patch Meister or someone else) and finds the tests
to look good, they can paste screenshots in the merge
request (for easier review) and advance it to Review
(tagging with the appropriate label on GitLab,
Patch::review). The Patch Meister is the only one to
advance to Patch::countdown and Patch::push.
I think these would be the main differences in the
countdown process, but I wasn't there six years ago.
You may want to read the current CG, which normally
should be up-to-date with these processes.
By the way: glad to meet you!
Cheers,
Jean
Re: Stepping down from Patch Meister role
On 2022-01-08 03:06, James wrote:
Hello,
I am going to stop doing the Patch countdown at the end of this month.
I'll continue for the next few weeks, but my last countdown will be
whatever the last date in January ends up being.
Thanks for your understanding.
Since James took over from me when I left the fold six years ago,
perhaps I can return the favour now. Fair warning: I left at the start
of what seems to have been a period of significant change, so I'm rather
out of touch with current terms ("patch" as I knew it is now "merge
request"?). With some coaching, and lashings of patience from the devs,
I'm willing to take it on.
Cheers,
Colin
Re: Stepping down from Patch Meister role
James, How much time do you spend per week as Patch Meister? If the time requirement is manageable, I could step in. I don't have lots of time to spend on Lilypond (hence my lack of current development work), but I could plan to spend some. Please help me understand the time you spend. Carl On 1/22/22, 11:09 AM, "lilypond-devel on behalf of Jonas Hahnfeld via Discussions on LilyPond development" wrote: Am Donnerstag, dem 13.01.2022 um 22:42 +0100 schrieb David Kastrup: > Kevin Barry writes: > > > Hi James, > > > > This is a big loss; you will be missed. Thank you for all of your hard work. > > > > > I want to stay a > > > developer and that conflicts both time-wise and with respect to > > > impartiality. > > > > Finding a non-developer to fill James's shoes sounds difficult. I > > would volunteer, but I still plan to contribute patches. > > git shortlog --author Lowe > > should be some indication that this is not a conflict of interest as > such. It may end up a conflict of resources. Yes, my initial message wasn't entirely clear, it's of course possible to contribute patches while being "Patch Meister". The "impartiality" aspect is that you should try to apply the same standards to your own submissions as to all other patches. So, there's around one week left until the end of January and this thread has more or less died down, thus last call for volunteers. Jonas
Re: Stepping down from Patch Meister role
Le 22/01/2022 à 20:31, Han-Wen Nienhuys a écrit : On Sat, Jan 22, 2022 at 7:09 PM Jonas Hahnfeld via Discussions on LilyPond development wrote: Finding a non-developer to fill James's shoes sounds difficult. I would volunteer, but I still plan to contribute patches. git shortlog --author Lowe should be some indication that this is not a conflict of interest as such. It may end up a conflict of resources. Yes, my initial message wasn't entirely clear, it's of course possible to contribute patches while being "Patch Meister". The "impartiality" aspect is that you should try to apply the same standards to your own submissions as to all other patches. So, there's around one week left until the end of January and this thread has more or less died down, thus last call for volunteers. One thought: maybe we could rotate the patch meister between different volunteers? That would also help with the impartiality: if one is this week's patch meister, you could simply leave your own MRs alone. Maybe James can comment here. Without ever having done these countdowns, my instinctive reaction is that it might work well, but it might also mean a bit more work at each countdown because you have to read the threads from the start if you haven't been following them on the previous countdown. Personally, while I'd be ready to do the countdowns if necessary, I'd prefer not to hold that responsibility on the long term because I tend to be somewhat too emotional with patches already. Also, one advantage of the countdown is that it enables someone without any technical experience to advance the project, thus freeing time for programmers. It has not been true with James that this has allowed someone to participate who would not have participated otherwise, given all his valuable documentation contributions, but there might be an opportunity to take now for finding someone who would not be in a position to immediately contribute in another way. Perhaps we could ask on the user list? Not sure how bug squad members were recruited when that existed, but lilypond-user would appear like the place where we have the best chances of finding new people ready to get involved. Jean
Re: Stepping down from Patch Meister role
On Sat, Jan 22, 2022 at 7:09 PM Jonas Hahnfeld via Discussions on LilyPond development wrote: > > > Finding a non-developer to fill James's shoes sounds difficult. I > > > would volunteer, but I still plan to contribute patches. > > > > git shortlog --author Lowe > > > > should be some indication that this is not a conflict of interest as > > such. It may end up a conflict of resources. > > Yes, my initial message wasn't entirely clear, it's of course possible > to contribute patches while being "Patch Meister". The "impartiality" > aspect is that you should try to apply the same standards to your own > submissions as to all other patches. > > So, there's around one week left until the end of January and this > thread has more or less died down, thus last call for volunteers. One thought: maybe we could rotate the patch meister between different volunteers? That would also help with the impartiality: if one is this week's patch meister, you could simply leave your own MRs alone. -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
Re: Stepping down from Patch Meister role
On Sat, Jan 8, 2022 at 11:07 AM James wrote: > I am going to stop doing the Patch countdown at the end of this month. > > I'll continue for the next few weeks, but my last countdown will be > whatever the last date in January ends up being. > > Thanks for your understanding. Thanks for your tireless work over the many years! Your persistent shepherding certainly has helped many contributions land that would have otherwise languished. -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
Re: Stepping down from Patch Meister role
Am Donnerstag, dem 13.01.2022 um 22:42 +0100 schrieb David Kastrup: > Kevin Barry writes: > > > Hi James, > > > > This is a big loss; you will be missed. Thank you for all of your hard work. > > > > > I want to stay a > > > developer and that conflicts both time-wise and with respect to > > > impartiality. > > > > Finding a non-developer to fill James's shoes sounds difficult. I > > would volunteer, but I still plan to contribute patches. > > git shortlog --author Lowe > > should be some indication that this is not a conflict of interest as > such. It may end up a conflict of resources. Yes, my initial message wasn't entirely clear, it's of course possible to contribute patches while being "Patch Meister". The "impartiality" aspect is that you should try to apply the same standards to your own submissions as to all other patches. So, there's around one week left until the end of January and this thread has more or less died down, thus last call for volunteers. Jonas signature.asc Description: This is a digitally signed message part
Re: Stepping down from Patch Meister role
Kevin Barry writes: > Hi James, > > This is a big loss; you will be missed. Thank you for all of your hard work. > >> I want to stay a >> developer and that conflicts both time-wise and with respect to >> impartiality. > > Finding a non-developer to fill James's shoes sounds difficult. I > would volunteer, but I still plan to contribute patches. git shortlog --author Lowe should be some indication that this is not a conflict of interest as such. It may end up a conflict of resources. -- David Kastrup
Re: Stepping down from Patch Meister role
Hi James, This is a big loss; you will be missed. Thank you for all of your hard work. > I want to stay a > developer and that conflicts both time-wise and with respect to > impartiality. Finding a non-developer to fill James's shoes sounds difficult. I would volunteer, but I still plan to contribute patches. Kevin
Re: Stepping down from Patch Meister role
Le 08/01/2022 à 11:06, James a écrit : Hello, I am going to stop doing the Patch countdown at the end of this month. I'll continue for the next few weeks, but my last countdown will be whatever the last date in January ends up being. Thanks for your understanding. You definitely deserve a ton of thanks. I was already amazed at your perseverance and regularity in this task, and I hadn't realized you had been doing it for so long. Thank you for keeping the project running during all these years. As said before off-list, thanks a lot for all the work you've been doing. I had a look at the mailing list archives and it appears you started doing the countdowns in February 2013, almost nine years ago. Your contributions reach back further than that (including testing of patches, not sure) and in any case that's an incredible time span! This also means we need to do at least one of two things: a) find a new person to take on the Patch Meister role and continue doing the countdowns, b) think about and agree on a "new" process to decide when patches can be pushed / merged. I personally like the countdown process for a number of reasons (as a contributor, it's nice to have a human "on the other side", and for reviewers it's relieving to have some amount of grace period). In the event that we have neither a) nor b) by the end of January, I can offer to take the role temporarily to "keep things going". That said, I'm definitely not a good fit in the longer term because I want to stay a developer and that conflicts both time-wise and with respect to impartiality. I also appreciate the current process. It ensures contributions from new contributors without commit access are not forgotten about and sets clear expectations for the moment at which a patch can be merged. If we can find another person for it, that would be ideal in my view. Best, Jean
Re: Stepping down from Patch Meister role
> As said before off-list, thanks a lot for all the work you've been > doing. Yes. Thanks, James! Werner
Re: Stepping down from Patch Meister role
On Jan 8, 2022, at 05:06, James wrote: > > I am going to stop doing the Patch countdown at the end of this month. > Thanks for the many years of steady contribution, James. — Dan
Re: Stepping down from Patch Meister role
Am Sa., 8. Jan. 2022 um 11:06 Uhr schrieb James : > > Hello, > > I am going to stop doing the Patch countdown at the end of this month. > > I'll continue for the next few weeks, but my last countdown will be > whatever the last date in January ends up being. > > Thanks for your understanding. > > -- > Regards > > James > Hi James, thanks a lot for all your work! You did a fabulous job! Best, Harm
Re: Stepping down from Patch Meister role
Am Samstag, dem 08.01.2022 um 10:06 + schrieb James: > Hello, > > I am going to stop doing the Patch countdown at the end of this month. > > I'll continue for the next few weeks, but my last countdown will be > whatever the last date in January ends up being. > > Thanks for your understanding. As said before off-list, thanks a lot for all the work you've been doing. I had a look at the mailing list archives and it appears you started doing the countdowns in February 2013, almost nine years ago. Your contributions reach back further than that (including testing of patches, not sure) and in any case that's an incredible time span! This also means we need to do at least one of two things: a) find a new person to take on the Patch Meister role and continue doing the countdowns, b) think about and agree on a "new" process to decide when patches can be pushed / merged. I personally like the countdown process for a number of reasons (as a contributor, it's nice to have a human "on the other side", and for reviewers it's relieving to have some amount of grace period). In the event that we have neither a) nor b) by the end of January, I can offer to take the role temporarily to "keep things going". That said, I'm definitely not a good fit in the longer term because I want to stay a developer and that conflicts both time-wise and with respect to impartiality. If you have thoughts on b), I'd suggest starting a new thread on the mailing list. Regards Jonas signature.asc Description: This is a digitally signed message part
Stepping down from Patch Meister role
Hello, I am going to stop doing the Patch countdown at the end of this month. I'll continue for the next few weeks, but my last countdown will be whatever the last date in January ends up being. Thanks for your understanding. -- Regards James
