On Tue, Jun 1, 2010 at 1:56 AM, Alexandru Băluț
wrote:
> The git log shows what you did. This would show how much you have to do
> (rough approximation, of course). btw, how exactly do you keep track of what
> you have to do? Having bugs assigned looks like a way of managing your
> todo-s.
One wa
On 6/1/2010 02:56, Alexandru Băluț wrote:
In the meanwhile, please assign the bugs, and spare others of
spending time on them. As a bonus, it would be nice to see
accurate numbers about how many bugs are on nobody's plate vs how
many are on somebody's plate. Data! :) At the mome
Hi Nikolay,
On Mon, May 31, 2010 at 18:27, Nikolay Sivov wrote:
> On 5/31/2010 20:01, Alexandru Băluț wrote:
>
> Hi Paul,
>
> I was wondering what is the best way to pick bugs, for a developer
> aspiring to fix nonspecific Wine bugs. Normally, our hero would look at the
> unassigned bugs to fi
On 5/31/2010 20:01, Alexandru Băluț wrote:
Hi Paul,
I was wondering what is the best way to pick bugs, for a developer
aspiring to fix nonspecific Wine bugs. Normally, our hero would look
at the unassigned bugs to find one to work on. For some bugs, a fix
appeared with no notification that so
Hi Paul,
I was wondering what is the best way to pick bugs, for a developer aspiring
to fix nonspecific Wine bugs. Normally, our hero would look at the
unassigned bugs to find one to work on. For some bugs, a fix appeared with
no notification that somebody is working on them, for example:
http://
