Sorry for the radio silence that followed this post in last 2011.
Starting today, I've joined the Android team at Google, working on the
Google Books app
This means that for the first time in three years, I'm now a full-time
user of JUnit again, not just a maintainer. Starting today, I'm going
to try to get back to one-week maximum latency for new code reviews
and communication around JUnit. If you've gotten stuck in the backlog
I've built up in the interim, feel free to re-forward and jump the
Also, if it feels like it's taking a long time to get a code review,
please feel free to use this list to ask other devs to take a first
look: often, the first 80% of improvements, especially around naming
and documentation, can be provided by any suitably experienced
Thanks for your patience and for supporting each other within the community.
On Mon, Oct 31, 2011 at 2:51 PM, David Saff <david@...> wrote:
> I've been very lucky for several years to had both a family and an
> employer that have left room for me to contribute to JUnit for free.
> However, for at least the next month, two launches are combining to
> absorb the lion's share of my time. One is named Micah, and is rather
> user-friendly most of the time, but has a somewhat draining
> maintenance schedule, and sporadic uptime. The other doesn't yet have
> a last name that we're sharing, although I expect the first name will
> be "Google".
> Thanks for understanding if your great questions and valuable patches
> are responded to with more delay over the coming weeks.
> David Saff