On Sun, Mar 17, 2013 at 7:34 AM, Brian LeRoux wrote:
> Was under the impression that there was a retirement path for
> incubation artifacts.
Retirement is for projects which are not longer maintained. I think
you meant graduation here, right?
It would be this document:
http://incubator.apache.or
Was under the impression that there was a retirement path for
incubation artifacts.
Also, want all traces of 'callback' to cease to exist. LOL
On Sun, Mar 17, 2013 at 6:33 AM, Christian Grobmeier
wrote:
> On Sun, Mar 17, 2013 at 6:20 AM, Brian LeRoux wrote:
>> https://github.com/cordova/apache
On Sun, Mar 17, 2013 at 6:20 AM, Brian LeRoux wrote:
> https://github.com/cordova/apache-board-reports/blob/master/2013-03.md
>
> lmk if I missed anything
I just read:
"Incubation retirement for
http://incubator.apache.org/projects/callback.html remains."
What do you mean by that? Maybe I can he
https://github.com/cordova/apache-board-reports/blob/master/2013-03.md
lmk if I missed anything
The question has come up about our continued support for:
- bada
- webos
- qt
- bb6 & bb7
Nobody is currently actively maintaining Bada, and Qt. However, I
could see us wanting to keep Qt around given Ubuntu Phone. There are
no new webOS devices, though rumours persist they could happen, it
seems
You could avoid the blocking queue if you dispatch the background thread's
runnable at the end of the UI thread's block.
I see you send a success callback as soon as the image is captured, but
before it is saved. This would improve throughput, but it might be even
more useful if you set the keepCa
