I'll be notifying yt-dev of this, and I hope we can have some consensus on this before it is accepted. Note that this places the 2.6 release date on March 1st. There may be areas that are not clear, in which case I would like to expand them.
Update 1: Oops, forgot about 2.5. Thanks, Cameron!
Update 2: Oops, forgot about 2.5. Thanks, Cameron!
I've read this 3 times to make sure I get all the details :-) I see this YTEP as the only way to make stable useful. I think the most difficult part of it, will be keeping up the Standards for Changes to the Code. But the more demanding people accepting PRs will be, the easier it will be to do frequent releases.
Do you think there are any technical approaches to helping keep the standards in place?
Yes, I think doing what we started recently will help, i.e. offloading work from humans beings. It's easier to bear if the person shouting at you is a machine and some of the things that you've mentioned in Standards can be automated like: checking if docstrings are present, checking if tests are present, and so on.
Okay. And if we end up with a write API to PRs, we can also immediately post the notice with the three items, so that reviewers will always see it as well. Something like, "Please comment verifying that you have done things X,Y,Z"
Do you mean that yt 2.5 release date is set for March 1st? Or is it really yt 2.6?