oxide team mailing list archive

[Dave Morley <davmor2@xxxxxxxxxxxxx>]

On 25/03/14 19:11, Jamie Strandboge wrote:
> On 03/25/2014 01:18 PM, David Barth wrote:
>> Le 25/03/2014 19:06, Alexandre Abreu a écrit :
>>> great news! so now we can land the pieces ...
>> Great news yes. As we discussed the next steps need to be:
>> - populate test the last silo with the oxide branches for webbrowser-app
>> (Olivier and yours)
> 
> I went ahead and created CItrain wiki pages:
>  * https://wiki.ubuntu.com/Process/Merges/Checklists/Oxide
>  * https://wiki.ubuntu.com/Process/Merges/TestPlans/Oxide
> 
> Right now we just need to have people review/update the TestPlan page. I threw
> some stuff in there but I'm not sure it is capturing everything. It is certainly
> lacking details/links to how to do some of the testing.
> 
> Checklists/Oxide can be thought of as a starting point for discussion. I know a
> lot of teams use autolandings, but currently I wrote the page somewhat with
> source package uploads in mind. It is intentionally not complete because we
> already have two branches (trunk and packaging) and may have more depending on
> how we decide to track upstream. In my mind, we don't need to iron out all these
> details now-- we have a sane peer review process for trunk, let's continue using
> it with source package uploads until we have time to think more about how we
> want to do landings.
> 
>> - Oxide MIR to be accepted (as a pre-requisite for the silo to be published,
>> because of main / universe cross deps)
> 
> as mentioned elsewhere in the thread, this is almost done
> 
> 
> 
> 
I would add grooveshark from the grooveshark scope and pumpkin smasher
gl based html5 app iirc to the list of apps to test.

-- 
You make it, I'll break it!

I love my job :)
http://www.ubuntu.com
http://www.canonical.com

Attachment: signature.asc
Description: OpenPGP digital signature