← Back to team overview

unity-dev team mailing list archive

Re: Desktop Unity branched for Raring

 

>
> I think starting next week, we should follow the plan we discussed on G+
> with Sam: having a wide user testing of this 0.9.10 branch,
> ensuring it introduce no regression from the current 0.9.9 one. If
> everything is ok, we can point and follow it for S. Sam is working and
> ensuring that we won't go again in the loop of regressions/fixes we had in
> the R serie. If this present again, we'll then diverge for S, but let's give
> 0.9.10 a chance.
>
> So plan for now:
> - start of next week (or even during week-end if people want to prepare a
> ppa): running 0.9.10 with current raring Unity, ensuring life is good,
> really do some days of dogfooding.
> - if by end of next week, reports are good, we'll flip the switch to track
> 0.9.10 in S. (will be daily releasing in the next ppa until S is opened)
>

I'm already running lp:compiz with unity ;-)

I can make a ppa though. It will take me five minutes to do. Aaaannd its done.

https://code.launchpad.net/~smspillaz/+archive/compiz-dev

(I'm assuming it will pull in the distro libnux)

Other bits and pieces:
1. I'm working on starting a framework so that we can write acceptance
tests for both the move, grid, resize and decor plugins. Those have a
high bug surface area, and also lots of people like to change them.
Ideally, we shouldn't be letting things in without tests, though I've
been letting other people just meet the threshold of code inspection +
manual testing for now, because I don't want to burden them with
making the code testable. (writing tests is easy, writing testable
code is not easy)

https://code.launchpad.net/~compiz-team/compiz/compiz.fix_1101026/+merge/159757

2. I've worked on making a simple GTest wrapper for any unity
autopilot tests which interact with compiz in a nontrivial way.

I note that some of these tests are failing anyways, and usually the
kinds of messages I get indicate that autopilot is broken and not
compiz. I can do a report on which failures I think are "wrong" so we
can fix autopilot and get these tests green.

I would have a merge link here, but it appears I forgot to bzr add a
few files, so I'll post that later.

We can use this binary as part of the autopkgtests. We just need to
install it somewhere and have it in another package.

I start another assignment next week and have a moot to prepare this
weekend. So my availability could be limited. But if you need anything
just ping me, or email here.

Best Regards,

Sam

> Sam, are you organizing this? ^
>
> Cheers,
> Didier
>
>
>
>>
>> Best Regards,
>>
>> Sam
>>
>>> --
>>> Stephen M. Webb  <stephen.webb@xxxxxxxxxxxxx>
>>>
>>> --
>>> Mailing list: https://launchpad.net/~unity-dev
>>> Post to     : unity-dev@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~unity-dev
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> --
>> Sam Spilsbury
>>
>
>
> --
> Mailing list: https://launchpad.net/~unity-dev
> Post to     : unity-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~unity-dev
> More help   : https://help.launchpad.net/ListHelp



--
Sam Spilsbury


Follow ups

References