Some status on this one, for those that aren't following JIRA...
We've been using the top of the yetus and yetus-test-patch-action trees publicly on https://github.com/lf-edge/eve . So far, it is working out very well, given some of the inherent limitations of GitHub Actions. After YETUS-1021 is committed, I think it would be useful to post on builds@ telling people in the ASF who are also using GitHub actions to try it out, noting that it is pre-release and should not be considered stable. It feels like a harmless way to not only get feedback but also, given the easier level of entry, more adoptees. Related news: I'd like to target getting a release out for Halloween if no one else is stepping up to cut one. Issues I'm looking at finishing for it: * YETUS-1021 - documentation update updates * In PR state * YETUS-992 - GitHub actions * will need release documentation updates to complete, so at least one more main source tree PR * YETUS-980 - jshint bug * PR open; timer expires soon * YETUS-1018 - circleci bug * PR open; timer expires soon * YETUS-908 and/or YETUS-1005 - CirrusCI bugs * not started * YETUS-987 - releasedocmaker 'single minor' file feature * started noodling on the problem, but might punt/do something different so that e.g., 0.11.0's change/release info shows up on the 0.11.1 change/release page as well * Given that 0.13.0 has some major incompatibilities, 0.13.1 seems inevitable bz I'm sure someone will find something that needs to get fixed right away, so i want to make sure we don't "lose" that info like we did with 0.11.0. Thoughts on the above? Thanks.
