> On Nov 13, 2018, at 4:20 AM, Sean Busbey <[email protected]> wrote:
>
> Awesome! Do we have any kind of timeline to a release that includes this?
> I'd like to get one going sooner rather than later so that downstream folks
> can update with fewer new things that might be the cause of any
> frustrations, since project restructuring is high risk for causing problems.
Not sure. Someone else will likely need to drive it. My Yetus time
right now is majorly dedicated to:
1: making it easier to use, especially for Not Jenkins. This was a
bunch of changes that I’ve pretty much got sitting in my fork now. The robots
rewrite makes Travis and Jenkins and lots of other systems now way smarter to
the point that in some cases the # of command line flags is cut down to less
than half (!) and some personalities aren’t particularly needed or useful
anymore (!).
2: getting it functional for my current work environment. Right now,
Yetus trunk isn’t anywhere close to working. The majority of the fixes I’ve
been writing lately have been in support of that. (Up next, a significant
smack to docker.sh—core parts of which haven’t been touched in years.)
On the positive side, after #2 is finished, I know I can say with
confidence that (at least a form of) Yetus really is being used outside of the
ASF and for non-Java projects. :)
On the negative side though, while I’ve been trying to contribute the
patches to the ASF, I need to work at a pace faster than the reviews are coming
in. Thus the fork, where every day the code diverges just that much more. :(
