papercuts-ninja team mailing list archive

[<druellan@xxxxxxxxxxxxxx>]

I really like this idea of having a "focused" cycle for an app in
particular, try to clear the backlogs a bit, but also be capable of
identify and "spin off" more critical core problems out of the scope, keep
track of them and help fixing them.

I'm not completely sure about the allocation of development cycles to GTK+
as a goal. As Timoty pointed out, this bugs can be difficult to find and
target if you're not tracking another bug already. I was thinking of it
more like a buffer of "spare cycles" to have in case you need to spin off
some issue.

But, hey! Lets try! I was not sure about the "application focus" thing and
now I love it!


On Wed, 28 Nov 2012 16:28:56 -0800 (PST), Timothy Arceri
<t_arceri@xxxxxxxxxxxx> wrote:
> Hi Chris,
>               Looks good. I'll try target a few more GTK bugs later on
> today. I'm not sure if we will be able to target 50 directly from whats
> already in the GTK package bug lists. But as we have already found a lot
of
> them are hidden away under other projects so it may take a little bit of
> detective work to uncover them.
> Anyway I really like the direction we are heading for this realese, a
lot
> of the bugs we have targets have been around for many many years so this
> papercuts release cycle should have a real impact on the user experence.
> 
> Keep up the good work guys,
> Tim
> 
> 
> 
> ________________________________
>  From: Chris Wilson <notgary@xxxxxxxxxx>
> To: Ubuntu Papercuts Ninjas <papercuts-ninja@xxxxxxxxxxxxxxxxxxx> 
> Sent: Thursday, 29 November 2012 10:17 AM
> Subject: [Papercuts-ninja] Milestone reorganisation.
>  
> 
> Hey Ninjas,
> 
> In the meeting we had last week, we decided it would be a good idea to
> move our focus away from a handful of individual apps and onto the UI
> foundation technologies found in Ubuntu. This came up after a number of
our
> Rhythmbox and Nautilus paper cuts turned out to be GTK+ bugs, so we
decided
> that GTK and Compiz would be our primary target for this (and
potentially
> all future) development cycles.
> 
> So I'm proposing the following
> 1) We allocate half a development cycle to GTK+, that is 50 paper cuts.
> 2) We allocate a quarter of a development cycle to Compiz, that is 25
> paper cuts.
> 3) We allocate the remaining quarter of the cycle to the biggest,
juiciest
> paper cuts we can find in Ubuntu's frontline apps.
> 4) I've also kept around the Rhythmbox and Nautilus milestones, since we
> had already started work on them.
> 
> I'd like to blog about this change in a couple of days, and before that
> I'd like to got some feedback from you lot. How does the new layout
look?
> 
> What now
> I've targeted a lot of bugs while reorganising the milestones, mostly to
> Nautilus, and it's probably that a lot of them are actually GTK+ bugs.
We
> should take a look at the currently targeted ones and make sure they're
> where they're supposed to be.
> 
> As for the Compiz paper cuts, MRC1, if that is your real name, you
> mentioned the existence of a lot of simple Compiz paper cuts. Can you
> please target as many of these bugs that are also manifesting as paper
cuts
> in Unity to the Compiz milestone?
> 
> Also, could our GTK+ ninjas please fill up the GTK+ milestone with as
many
> paper cuts as possible? We've only got a few and I'm sure there's tons
of
> them out there.
> 
> So, thoughts anyone?
> 
> Chris
> _______________________________________________
> Mailing list: https://launchpad.net/~papercuts-ninja
> Post to     : papercuts-ninja@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~papercuts-ninja
> More help   : https://help.launchpad.net/ListHelp