To add to the above, hackathons would make sense in the lead up to the
feature freeze IMO to get things through the door, but not necessarily
afterwards (debatable). And they can be flexible too; I suspect once people
start on reviewing something they'll be much more likely to see it through
to com
I like the idea and we would be willing to take part (no committers here
but I'm sure we can help).
I think it better to pick some JIRAs per 2-3 weeks and have people review
> them. In my experience, it is hard to synchronize all people across
> companies during one 72 hour slot.
It is hard, but
That could work as well. My goal is that we figure out how to resource and
focus on this for a bit.
On Fri, Apr 6, 2018, 5:02 PM sankalp kohli wrote:
> I think it better to pick some JIRAs per 2-3 weeks and have people review
> them. In my experience, it is hard to synchronize all people across
I think it better to pick some JIRAs per 2-3 weeks and have people review
them. In my experience, it is hard to synchronize all people across
companies during one 72 hour slot.
On Thu, Apr 5, 2018 at 9:48 PM, Nate McCall wrote:
> Per Kurt's point in our release thread, we have a lot to do here
Per Kurt's point in our release thread, we have a lot to do here.
What do folks feel about setting aside a 72hr period at some point soon
where we get some allotment from our employers to spend a window or two of
time therein reviewing patches?
I have seen a couple of other ASF communities do thi
