1.1.1 was just released, and 1.2 is close to a release. That, plus Thanksgiving in the US (where most Spark committers AFAIK are located), probably means a temporary lull in committer activity on non-critical items should be expected.
On Mon Nov 24 2014 at 9:33:27 AM York, Brennon <brennon.y...@capitalone.com> wrote: > All, I just finished the SPARK-3182 feature and, for me, its raised a > larger question of how to ensure patches that are awaiting review get noted > / tagged upstream. Since I don’t have access writes to assign the above > issue to myself I can’t tag it as “In Progress” like Matei mentioned so, at > this rate, its just going to sit in the queue. Did I miss something on the > “Contributing to Spark” page, is there a ‘tribal-knowledge’ way to let a > set of commiters know that patches are ready, or is it that everyone is > already too slammed and we’re all waiting diligently? :) Just trying to get > some clarity on this topic, thanks! > ________________________________________________________ > > The information contained in this e-mail is confidential and/or > proprietary to Capital One and/or its affiliates. The information > transmitted herewith is intended only for use by the individual or entity > to which it is addressed. If the reader of this message is not the > intended recipient, you are hereby notified that any review, > retransmission, dissemination, distribution, copying or other use of, or > taking of any action in reliance upon this information is strictly > prohibited. If you have received this communication in error, please > contact the sender and delete the material from your computer. >
