[15:30] <alesage> Hi all, we'll have one of our monthly Canonical Product Strategy meetings shortly
[15:30] <mmrazik> hi
[15:31] <alesage> hi mmrazik, do you want to lead?
[15:31] <mmrazik> alesage: do you know how the bot works?
[15:31] <alesage> mmrazik, no--first time here :)
[15:31] <mmrazik> then I'll start the meeting :)
[15:31] <mmrazik> #startmeeting
[15:31] <meetingology> Meeting started Tue Feb 28 15:31:46 2012 UTC.  The chair is mmrazik. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:31] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[15:32] <mmrazik> lets wait for a minute or so
[15:32] <mmrazik> the only topic today is a short talk about Static Code Analysis and what we do in Canonical with Unity et al
[15:33] <mmrazik> [TOPIC] Static Code Analysis (Coverity)
[15:33] <mmrazik> alesage: I think we can start
[15:33] <alesage> ok thanks mmrazik
[15:34] <alesage> so this will be a short chat about our use of Coverity
[15:34] <alesage> which is a static analyzer
[15:35] <alesage> here's our wiki page for our Coverity integration project:
[15:35] <alesage> https://wiki.ubuntu.com/CanonicalProductStrategy/Coverity
[15:35] <alesage> and here's a link to the company's site: http://coverity.com/products/static-analysis.html
[15:36] <alesage> we're using static analysis as a means to improve quality:
[15:36] <alesage> the idea behind "static analysis" is kind-of a step further than what a compiler offers your C/C++/Java/etc. code
[15:37] <alesage> in the case of Coverity, for example, the static analyzer sits on GCC and finds bugs in our code
[15:37] <alesage> by producing 'models' of the execution--
[15:38] <alesage> specifically by running 'checkers', which find common (or not so common ;) ) errors
[15:38] <alesage> I'll link to a list of these checkers . . .
[15:38] <alesage> https://wiki.ubuntu.com/CoverityCheckerDictionary
[15:39] <alesage> so taking DIVIDE_BY_ZERO as an example,
[15:39] <alesage> here's a condition that might take an exceptional condition to encounter in production, e.g.
[15:40] <alesage> but Coverity finds this using its sophisticated analysis
[15:41] <alesage> so we wanted to add this to our process for developing Ubuntu
[15:41] <alesage> at the moment our licensing covers everything that's a dependency of Unity
[15:42] <alesage> and there's talk about expanding--we'll see how the evaluation goes
[15:42] <alesage> are there any questions at this point?
[15:42] <gema_> o/
[15:42] <alesage> I have to thank tvoss for this link, meanwhile: http://drdobbs.com/open-source/232601492
[15:42] <alesage> gema_, go ahead
[15:42] <gema_> alesage: are you raising bugs as you find them? are you gettting a lot of false positivies?
[15:43] <alesage> gema_ excellent question
[15:43] <alesage> so my part of the project has been a "syncing" tool
[15:43] <alesage> which submits bugs to Launchpad when these defects are found
[15:43] <gema_> automatically?
[15:43] <alesage> automatically--
[15:43] <gema_> agreed :)
[15:44] <alesage> the scanner is run as part of a Jenkins/Continuous Integration process
[15:44] <alesage> so when we get a build, the scanner runs and finds its Coverity defects,
[15:44] <alesage> and then a little Python script interprets these and submits them to Launchpad
[15:44] <alesage> where they enter the normal Ubuntu developer workflow
[15:44] <alesage> let me get the link for some existing bugs . . .
[15:46] <alesage> https://bugs.launchpad.net/~coverity-uploader
[15:46] <alesage> so we haven't found a full set as yet, and it's still to early to show our 'defect density' (ref. the link above)
[15:47] <alesage> and gema_ as this is still and informal process I'm not aware of complaints about false positives
[15:47] <gema_> alesage: I am very impressed, looks pretty good
[15:47] <mmrazik> this is up and running for about a week
[15:47] <mmrazik> after some time we might want to do some queries and get the % of invalid bugs or something like that
[15:47] <alesage> gema_ yeah it's fun to go through the defects
[15:47] <mmrazik> that should give us some idea about the false positives
[15:47] <gema_> mmrazik: ack
[15:48] <alesage> let's take an example
[15:48] <alesage> https://bugs.launchpad.net/bamf/+bug/937402
[15:48] <alesage> so here's an uninitialized variable somewhere deep in bamf
[15:49] <alesage> you see that you get a little code snippet in the bug body there
[15:49] <alesage> and also an attachment with a prettier rendering of the source code
[15:50] <alesage> Coverity offers a more sophisticated product called the "Integrity Manger"
[15:50] <alesage> most of the features of which this 'syncer' is offering to Launchpad users
[15:50] <alesage> one more interesting case:
[15:51] <alesage> https://bugs.launchpad.net/libindicator/+bug/937387
[15:51] <alesage> here's a case in which Coverity has found the same defect in multiple projects
[15:52] <alesage> in this case the root of the problem is in libindicator
[15:52] <alesage> and ted has tackled and ably squashed the bug
[15:53] <alesage> but note that Coverity's tracking of defects enables us to keep the defects in one place, as one Launchpad bug
[15:53] <alesage> any questions at this point?
[15:55] <alesage> so honestly this is my first encounter with static analysis
[15:56] <alesage> do people have more extensive experience with this, or with Coverity itself?
[15:58] <alesage> so we'll have some metrics to offer in our Quality Hour blog at some point in the future
[15:58] <alesage> please stay tuned :)
[15:58] <alesage> and feel free to follow up with me for questions anytime
[15:59] <alesage> thanks all--anything else mmrazik?
[15:59] <mmrazik> any last questions?
[15:59] <mmrazik> in that case -- thank you for the meeting and lets meet in a month :)
[15:59] <mmrazik> bb
[15:59] <mmrazik> #endmeeting
[15:59] <meetingology> Meeting ended Tue Feb 28 15:59:52 2012 UTC.
[15:59] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-28-15.31.moin.txt
[15:59] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-28-15.31.html
[15:59] <lynxman> \o
[16:00] <alesage> lynxman, yes
[16:00] <lynxman> alesage: ah no worries, just waiting for the next meeting :)
[16:00] <justinlw> \o
[16:01] <utlemming> \o
[16:02] <jamespage> o/
[16:02] <arosales> \o
[16:02] <smb> \o
[16:04] <jamespage> utlemming, you chaired last week right?
[16:04] <zul> hi
[16:04] <utlemming> I did
[16:04] <alesage> yes utlemming
[16:04] <jamespage> ah - guess that means zul is in the chair then :-)
[16:05] <lynxman> zul: chair it like a boss
[16:05] <zul> ooh quick meeting then
[16:05] <zul> #startmeeting
[16:05] <meetingology> Meeting started Tue Feb 28 16:05:10 2012 UTC.  The chair is zul. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:05] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:05] <zul> so this is the server team meeting so lets get started
[16:05] <zul> #topic Review ACTION points from previous meeting
[16:05] <adam_g> o/
[16:05] <zul> i guess there was none?
[16:06] <zul> #topic Precise Development
[16:06] <zul> so beta-1 is next week isnt it?
[16:06] <ogra_> in two days
[16:06] <arosales> beta-1 testing is now open
[16:06] <zul> damn...i need a better calendar
[16:06] <zul> does anyone want to drive this topic?
[16:06] <zul> Daviey: ^^^
[16:07] <zul> arosales: ^^^
[16:07] <arosales> Any Feature Freeze expectations to note?
[16:07] <arosales> zul: keystone is going well?
[16:08] <zul> arosales: yeah..but it seems to have broke some things
[16:08] <zul> service tokens have changed so people upstream are grossing about it
[16:08] <zul> but yeah
[16:09] <arosales> ok, thanks for working on that zul
[16:09] <arosales> Any work items folks would like to talk about
[16:09] <arosales> http://status.ubuntu.com/ubuntu-precise/ubuntu-server.html
[16:09] <zul> the debian-installer one should be fixed now
[16:09] <zul> bug 923681
[16:10] <arosales> thats good news
[16:10] <zul> anything else?
[16:11] <arosales> nothing more from me on this topic.
[16:11] <zul> anyone want to bring anything else up?
[16:12]  * arosales still looking at work item status, but will work on that offline
[16:12] <zul> if not
[16:12] <zul> #topic Ubuntu Server Team Events
[16:12] <zul> ODS is coming up in April, UDS is coming up after that
[16:12] <zul> any events people are going to?
[16:12] <Daviey> hola, i thought utlemming was charining?
[16:13] <arosales> m_3 is @ Strata
[16:13] <zul> Daviey: that was last week
[16:13] <utlemming> Daviey: that was last week
[16:13] <utlemming> :)
[16:13] <Daviey> utlemming: wiki said otherwise.. anyway, sorry for the noise.
[16:14] <zul> anyways i dont think there is any other events coming up
[16:14] <zul> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:14] <hggdh> hi
[16:15] <zul> hey hggdh
[16:15] <hggdh> only... Beta testing, and testing, folks ;-)
[16:15] <hggdh> ..
[16:15] <zul> cool
[16:15] <zul> any questions for hggdh
[16:16] <zul> if not quickly moving on:
[16:16] <zul> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:16] <zul> hi smb
[16:16] <smb> From things going on I believe the only thing worth noting from my side is for Lucid where I had been looking at a bug about spinlocking that lead to even more determined thinking of dropping the whole ec2 patch delta and moving back to the basic 2.6.32 kernel for EC2 as well. The decision to go with the special patch set was based on one missing
[16:17] <smb> patch. And we know about that now. Of cousrse this needs a lot of testing before actually going on with that
[16:17] <zul> cool
[16:17] <smb> Otherwise open for question if there are
[16:17] <smb> ..
[16:17] <zul> any questions?
[16:18]  * smb thinks no
[16:18] <zul> everybody must be working away
[16:18] <zul> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:18] <zul> hi rbasak
[16:18] <rbasak> hello!
[16:19] <zul> anything to bring up
[16:19] <rbasak> Nothing to report.
[16:19] <rbasak> Any questions for me?
[16:19] <rbasak> Oh - the ARM team has now merged into platform, QA etc.
[16:20] <zul> if not moving on
[16:20] <zul> #topic Open Discussion
[16:20] <zul> anything to bring up
[16:20] <arosales> \o
[16:20] <arosales> adam_g: Did you get any more info on bug 924739?
[16:21] <arosales> zul, mind if we go through at least the high bugs @ http://status.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:22] <zul> arosales: go ahead
[16:22] <arosales> zul, ok thanks.
[16:22] <arosales> bug 883988
[16:22] <arosales> adam_g: were you working on this one?
[16:23] <arosales> perhaps similar to bug 779311
[16:23] <arosales> bug 893926
[16:24] <Daviey> ^^ i think we should try and punt that to iamfuzz
[16:24] <arosales> no recent updates on this one, any one have any information on EUC?
[16:24] <Daviey> (Sorry for being largely absent.)
[16:24] <arosales> bug 911812
[16:25] <roaksoax> arosales: haven't taken care of it as I've been busy with the MaaS stuff
[16:25] <arosales> roaksoax: roger that, still on your radar though?
[16:25] <roaksoax> arosales: yest, this week i should definitely get it done (gfinally)
[16:26] <arosales> roaksoax: cool, thanks :-)
[16:26] <arosales> bug 923681
[16:26] <arosales> zul already covered that
[16:26] <arosales> bug 925024
[16:27] <arosales> hallyn: any more insights into 925024?
[16:27] <arosales> or still waiting on feedback from Brad?
[16:28] <arosales> bug 850443
[16:28] <adam_g> arosales: sorry, internet dropped. re squid bug, talked to daviey about this yesterday and i have better direction now than last week.  i pinged upstream about bug 883988, the glance db migration bug seems to be deferred upstream till next cycle, so ill probably try to come up with a fix myself for that.
[16:28] <hallyn> arosales: fix is heading into the kernel
[16:28] <arosales> hallyn: great, thanks.
[16:29] <arosales> Daviey: is 850443 yours?
[16:29] <arosales> adam_g: Thanks for the update and continuing to work on that squid.conf issue.
[16:29] <arosales> bug 928383
[16:30] <arosales> look to be fairly new
[16:30] <adam_g> arosales: i think that one is invalid, ill mark it so
[16:30] <Daviey> arosales: currently blocked on upstream bug tracker comments
[16:30] <arosales> adam_g: Thanks for updating 928383
[16:31] <arosales> Daviey: ok, thanks.
[16:31] <arosales> bug 928990
[16:32] <arosales> Looks like smoser filed this one on  Feb 8th
[16:32] <arosales> smoser: utlemming: any further insights on 928990?
[16:33] <arosales> bug 929780
[16:33] <adam_g> zul: was that console.ring permission one fixed with the proper refresh of the nova console patch we carry?
[16:34] <zul> i think thats fixed
[16:34] <rbasak> what's the instance directory's permissions?
[16:34] <rbasak> or is that the fix?
[16:34] <zul> thats the fix
[16:34] <arosales> zul, could you update that bug?
[16:34] <zul> ill double check one more time today :(
[16:34] <arosales> solid, thanks zul :-)
[16:35] <arosales> zul: that covers the high bugs, there is a few pings out there for folks still . . .
[16:36] <arosales> but perhaps they will catch the log or back scroll
[16:36] <lynxman> Daviey: did you get to talk with jdstrand about the puppet security update?
[16:36] <Daviey> lynxman: not as yet
[16:36] <zul> anything else?
[16:36] <rbasak> We should have a separate agenda item for Precise Server release bugs really.
[16:37] <zul> we should not have any bugs ;)
[16:37] <rbasak> Action item for zul: fix all the bugs :)
[16:37] <zul> yeah thats not going to happen :P
[16:38] <lynxman> zul: if there's anyone that can do it, it's you
[16:38] <zul> if anyone thing has any else
[16:39] <zul> #topic Announce next meeting date and time
[16:39] <zul> next week same bat time same bat channel
[16:39] <zul> thanks for coming
[16:39] <zul> #endmeeting
[16:39] <meetingology> Meeting ended Tue Feb 28 16:39:25 2012 UTC.
[16:39] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-28-16.05.moin.txt
[16:39] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-28-16.05.html
[16:40] <arosales> who is the chair for the next meeting?
[16:40] <arosales> hallyn next on the list, but I think he may have just dropped
[16:41] <arosales> ok, thanks folks -- enjoy the rest of your day.
[16:41] <arosales> zul thanks for chairing
[17:00] <ppisati> o/
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <meetingology> Meeting started Tue Feb 28 17:00:05 2012 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:00] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <apw> o/
[17:00] <cking> o/
[17:00] <herton> o/
[17:00] <tgardner> o/
[17:00] <ogasawara> o/
[17:00] <sforshee> o/
[17:00] <henrix> o/
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:00] <bjf> o/
[17:00] <ppisati> P/omap4: a new kernel (3.2.0-1407.9) was cut, rebased on top of 3.2.0-17.27, with fixes for usb musb (lp 927860), led heartbeat (lp 905445) and smsc95xx cmdline macaddr option (lp 937051).
[17:00] <ppisati> M/omap4: to reserve >= 2GB of memory (lp 861296) the memory layout was changed from a 2G/2G to a 3G/1G split - next SRU kernel will contain this fix.
[17:00] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-precise/canonical-kernel-distro-team-ubuntu-12.04-beta-1.html
[17:01] <ogasawara> || apw        || hardware-p-kernel-boot                || 4 work items ||
[17:01] <ogasawara> ||            || hardware-p-kernel-config-review       || 6 work items ||
[17:01] <ogasawara> ||            || hardware-p-kernel-delta-review        || 3 work items ||
[17:01] <ogasawara> || sconklin   || servercloud-p-ceph                    || 1 work item  ||
[17:01] <ogasawara> If your name is in the above table, please review your Beta-1 work
[17:01] <ogasawara> items.  If they won't be closed by Thursday, please push them out to
[17:01] <ogasawara> Beta-2.
[17:01] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Blueprint: hardware-p-kernel-power-management (cking)
[17:02] <cking> Power Management:
[17:02] <cking>  * Bluetooth power consumption in suspend
[17:02] <cking>    http://zinc.canonical.com/~cking/power-benchmarking/bluetooth-suspend
[17:02] <cking>  * Background colour with DPMS off
[17:02] <cking>    http://zinc.canonical.com/~cking/power-benchmarking/background-dpms
[17:02] <cking>  * Call for testing: latest RC6 fixes, https://wiki.ubuntu.com/Kernel/PowerManagementRC6
[17:02] <cking>    Please *re-test* if you haven't already done so. Thanks to Leann Ogasawara
[17:02] <cking>    for organising this.
[17:02] <cking> ..
[17:02] <jsalisbury> [TOPIC] Status: Precise Development Kernel (ogasawara)
[17:02] <ogasawara> The archive remains frozen for the upcoming Beta-1 release on Thursday.
[17:02] <ogasawara> We received a Beta Freeze exception last week to upload a fix for the
[17:02] <ogasawara> RC6 patch we applied.  This has received positive testing feedback and
[17:02] <ogasawara> it looks promising that we will be able to ship with RC6 enabled by
[17:02] <ogasawara> default.
[17:02] <ogasawara> We have been queueing patches for the first post Beta-1 upload.  This
[17:02] <ogasawara> will include a rebase to the latest v3.2.8 upstream stable release.  We
[17:02] <ogasawara> will need to coordinate our upload with the planned gcc-4.6 upload.
[17:03] <ogasawara> Important upcoming dates:
[17:03] <ogasawara>  * Thurs Mar 01 - Beta 1 (~2 days)
[17:03] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's (apw)
[17:03] <apw> Currently we have 74 CVEs on our radar, two new CVEs were added this week.
[17:03] <apw> See the CVE matrix for the current list:
[17:03] <apw>  
[17:03] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <apw>  
[17:03] <apw> Overall the backlog is broadly unchanged this week, we have closed one
[17:03] <apw> of the new CVEs and the other is already fixed for a number of releases:
[17:03] <apw>  
[17:03] <apw> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:03] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:03] <apw>  
[17:03] <apw> ..
[17:04] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy (bjf/herton)
[17:04] <bjf> Here is the status for the main kernels, until today (Feb. 28):
[17:04] <bjf>  
[17:04] <bjf>  * Hardy - 2.6.24-31.99     - Ready for copy to -updates
[17:04] <bjf>  * Lucid - 2.6.32-39.86     - In regression testing
[17:04] <bjf>  * Maverick - 2.6.35-32.66  - In regression testing
[17:04] <bjf>  * Natty - 2.6.38-13.56     - In regression testing
[17:04] <bjf>  * Oneiric - 3.0.0-16.29    - In regression testing
[17:04] <bjf>  
[17:04] <bjf> Current opened tracking bugs details:
[17:04] <bjf>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:04] <bjf>  
[17:04] <bjf> For SRUs, SRU report is a good source of information:
[17:04] <bjf>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:04] <bjf>  
[17:04] <bjf> Future stable cadence cycles:
[17:04] <bjf>  * https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock
[17:04] <bjf> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:05] <jsalisbury> Thanks everyone
[17:05] <jsalisbury> #endmeeting
[17:05] <meetingology> Meeting ended Tue Feb 28 17:05:16 2012 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-28-17.00.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-02-28-17.00.html
[17:05] <cking> thanks jsalisbury
[17:05] <apw> jsalisbury, ta
[17:05] <kamal> jsalisbury: thanks
[17:06] <tgardner> sconklin, your name is on ogasawara's list: http://status.ubuntu.com/ubuntu-precise/canonical-kernel-distro-team-ubuntu-12.04-beta-1.html
[17:06] <sconklin> looking
[17:07] <sconklin> I'm also in another meeting . . .
[17:07] <tgardner> sconklin, ceph evaluation I think
[17:08] <sconklin> I'll get it looked at today and see whether it needs to be deferred. I think it can probably be done
[17:08] <sconklin> well, the tests can be written, but there's still no place for them to run in QA
[17:09] <sconklin> I think it has to be deferred for that reason
[17:11] <ogasawara> sconklin: deferred to beta-2?  or Q?
[17:12] <sconklin> ogasawara: to Q, as there won't be any tests other than SRU testing in QA for the kernel during this cycle, best I can tell
[17:12] <ogasawara> sconklin: ack
[17:12] <sconklin> ogasawara: although if there's value in standing up some tests in some private test instances, we can pursue that
[17:13] <sconklin> I don't know who would know how important that is
[17:15] <ogasawara> sconklin: I'd talked to clint about some other work items assigned to our team in that blueprint and we postponed them as there were workarounds and it is a low priority blueprint
[17:17] <sconklin> ack, should I talk to clint about postponing cep QA testing?
[17:18] <ogasawara> sconklin: well, I just postponed it for you :)
[17:18] <sconklin> thanks
[17:18] <ogasawara> sconklin: if I hear of any backlash, I'll let you know
[17:19] <sconklin> ack, we can do something less than full-blown QA testing if  they just need some sanity checks