Boris Renski wrote:
> There are a couple of additional things we are working on driver
> verification front that, I believe, it is now time to socialize with the
> dev community:
>
> 1. In addition to the scare tactic of deprecating the code for those
> that don't test their drivers, we also want
On 02/13/2014 09:51 AM, Avishay Traeger wrote:
"Walter A. Boring IV" wrote on 02/13/2014 06:59:38
PM:
What I would do different for the Icehouse release is this:
If a driver doesn't pass the certification test by IceHouse RC1, then we
have a bug filed
against the driver. I would also put a w
On Thu, Feb 13, 2014 at 10:30 AM, Dean Troyer wrote:
> On Thu, Feb 13, 2014 at 4:51 AM, Thierry Carrez
> wrote:
>
>> John Griffith wrote:
>> > To add some controversy and keep the original intent of having only
>> > known tested and working drivers in the Cinder release, I am going to
>> > propos
"Walter A. Boring IV" wrote on 02/13/2014 06:59:38
PM:
> What I would do different for the Icehouse release is this:
>
> If a driver doesn't pass the certification test by IceHouse RC1, then we
> have a bug filed
> against the driver. I would also put a warning message in the log for
> that
On Thu, Feb 13, 2014 at 9:30 AM, Dean Troyer wrote:
> Are any of these drivers new for Icehouse? I think adding broken drivers
> in Icehouse is a mistake. The timing WRT Icehouse release schedule is
> unfortunate but so is shipping immature drivers that have to be supported
> and possibly depre
On Thu, Feb 13, 2014 at 9:59 AM, Walter A. Boring IV
wrote:
> On 02/13/2014 02:51 AM, Thierry Carrez wrote:
>>
>> John Griffith wrote:
>>>
>>> So we've talked about this a bit and had a number of ideas regarding
>>> how to test and show compatibility for third-party drivers in Cinder.
>>> This has
On Thu, Feb 13, 2014 at 4:51 AM, Thierry Carrez wrote:
> John Griffith wrote:
> > To add some controversy and keep the original intent of having only
> > known tested and working drivers in the Cinder release, I am going to
> > propose that any driver that has not submitted successful functional
>
On 02/13/2014 02:51 AM, Thierry Carrez wrote:
John Griffith wrote:
So we've talked about this a bit and had a number of ideas regarding
how to test and show compatibility for third-party drivers in Cinder.
This has been an eye opening experience (the number of folks that have
NEVER run tempest b
John Griffith wrote:
> So we've talked about this a bit and had a number of ideas regarding
> how to test and show compatibility for third-party drivers in Cinder.
> This has been an eye opening experience (the number of folks that have
> NEVER run tempest before, as well as the problems uncovered
Hey,
So we've talked about this a bit and had a number of ideas regarding
how to test and show compatibility for third-party drivers in Cinder.
This has been an eye opening experience (the number of folks that have
NEVER run tempest before, as well as the problems uncovered now that
they're trying
10 matches
Mail list logo
