Re: [Desktop] Release Meeting 2012-08-31

2012-08-31 Thread Sebastien Bacher
Reply to myself, we had a pending action: "ask TheMuso to put together a list of tests worth focusing on for accessibility" I didn't get a reply from Luke but here as the basic things to test: - boot the liveCD, enable screen reader, check that it's working in

[QA Community] Release Meeting 2012-08-31

2012-08-31 Thread Nicholas Skaggs
=== What was done engineering wise? === * Closed compiz / unity testing * UDS-R planning * Testing the daily isos in advance of beta * Improved bug reporting instructions for iso's * Adding new testcases for new ubiquity features === What's about to land that might impact the other teams and

[Lubuntu] Release Meeting 2012-08-31

2012-08-31 Thread Julien Lavergne
Hi, === What was done engineering wise? === * Work on the new icon theme. * Adjustments of the default settings for the new artwork * Integration continue with the new icon theme (patch for the terminal, the mail application ...). === What's about to land that might impact the other teams and

Re: [Ubuntu One] Release Meeting 2012-08-31

2012-08-31 Thread Joshua Hoover
On 08/30/2012 06:51 PM, Kate Stewart wrote: > On Thu, 2012-08-30 at 16:15 -0500, Joshua Hoover wrote: > >> === What's about to land that might impact the other teams and release >> as a whole? === >> >> * [FFE] Ubuntu One integration with Q sync indicator - Won't be landing >> until the week of B

Re: [Desktop] Release Meeting 2012-08-31

2012-08-31 Thread Sebastien Bacher
Le 31/08/2012 15:24, Jamie Strandboge a écrit : > * system-config-printer: Integrated automatic driver download from >OpenPrinting, as Jockey as provider for that feature is not present any more Was this captured in a blueprint? I know my team looked at what jockey was doing before and would

Re: [Desktop] Release Meeting 2012-08-31

2012-08-31 Thread Jamie Strandboge
On Fri, 2012-08-31 at 00:01 +0200, seb128 wrote: > === What was done engineering wise? === > * system-config-printer: Integrated automatic driver download from > OpenPrinting, as Jockey as provider for that feature is not present any more Was this captured in a blueprint? I know my team looked

[PS] Release Team meeting 20120831

2012-08-31 Thread Alan Pope
== What was done engineering wise? == * quantal - Fixes in preparation of releasing OpenGL ES enabled compiz together with new Unity, bamf and nux * precise - Work on renaming utouch to geis == What's about to land that might impact the other teams and release as a whole? == * compiz

Re: [Foundations] Release Meeting 2012-08-29

2012-08-31 Thread Oliver Grawert
hi, Am Freitag, den 31.08.2012, 14:09 +0200 schrieb Sebastien Bacher: > Le 31/08/2012 12:43, Oliver Grawert a écrit : > > * XDG_RUNTIME_DIR spec to be done the coming week > Does it mean it will be in beta1 or miss it? We really wanted to test > the XDG_RUNTIME_DIR codepaths in desktop components

Re: [Desktop] Release Meeting 2012-08-31

2012-08-31 Thread Oliver Grawert
hi, Am Freitag, den 31.08.2012, 00:01 +0200 schrieb seb128: > * The dropping of unity-2d creates issues, especially on arm (still not > 3d drivers for the pandaboard) that need to be sorted out > this landed last week (as reported in the foundations report), the 3D drivers are now the default on

Re: [Foundations] Release Meeting 2012-08-29

2012-08-31 Thread Sebastien Bacher
Le 31/08/2012 12:43, Oliver Grawert a écrit : * XDG_RUNTIME_DIR spec to be done the coming week Does it mean it will be in beta1 or miss it? We really wanted to test the XDG_RUNTIME_DIR codepaths in desktop components for beta1 since beta2 would be late to start getting feedback on that... Ch

subject: [Ubuntu Studio] Release Meeting 2012-08-31

2012-08-31 Thread Scott Lavender
=== What was done engineering wise? === * some work was done on xfce 4.10 plugins * almost wrapping up adding publishing work flow/apps/menu * fixing help menu entry === What's about to land that might impact the other teams? === not aware of anything === Release Notes === n/a === Summary of bug

[Foundations] Release Meeting 2012-08-29

2012-08-31 Thread Oliver Grawert
== What was done engineering wise? == * boot/upstart, Stateful re-exec: Continued work to get post re-exec environment sane * more work on gwibber py3 port * bug triage of package installation failures / distribution upgrades * gathering of and research into BootDmesg from bug reports to determ

Re: Release Process concerns (QA) and suggestions

2012-08-31 Thread Gema Gomez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Stéphane, thanks for your answer, it gives us many clues to improve coverage at milestones, which is good news. On 30/08/12 19:53, Stéphane Graber wrote: > On 08/28/2012 09:38 AM, Gema Gomez wrote: I'm going to start by > saying that we never res

Re: Release Process concerns (QA) and suggestions

2012-08-31 Thread Gema Gomez
On 31/08/12 10:12, Jean-Baptiste Lallement wrote: > On 08/31/2012 07:45 AM, Martin Pitt wrote: >> Scott Kitterman [2012-08-30 16:25 -0400]: >>> If we try and be too specific about criteria then we're going to get >>> rules >>> lawyers complaining we didn't follow the criteria rather than >>> applyi

[Xubuntu] Release Meeting 2012-08-31

2012-08-31 Thread Pasi Lallinaho
=== What was done engineering wise? === * A massive UI update; wallpaper, LightDM, documentation looks, Ubiquity slideshow... === What's about to land that might impact the other teams and release as a whole? === * Working to get indicators back (GTK2) for Xubuntu, Lubuntu, US === Summary of

Re: [QA] Release Meeting 2012-08-31

2012-08-31 Thread Jean-Baptiste Lallement
On 08/30/2012 07:30 PM, Gema Gomez wrote: Hi, Here is the QA report this week: === Release Testing === Quantal Testing *Builds* http://reports.qa.ubuntu.com/reports/isotesting/builds/quantal.html *Testing* https://jenkins.qa.ubuntu.com/view/Quantal * ISO Testing: - Desktop: - No

Re: Release Process concerns (QA) and suggestions

2012-08-31 Thread Jean-Baptiste Lallement
On 08/31/2012 07:45 AM, Martin Pitt wrote: Scott Kitterman [2012-08-30 16:25 -0400]: If we try and be too specific about criteria then we're going to get rules lawyers complaining we didn't follow the criteria rather than applying common sense. I see this happening with Feature Freeze exception