[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Public WebGL] Re: specification/implementation cadence
So you plan to have no webgl 2.1 draft spec till mid 2017, release spec 6 months later start of 2018 and fully grown publicly released implementation by a few months later in spring 2018?
I might ignore a few things, but i dont see how that changes that if you want to hit or exceed the linear projection, you need to compress all the work that usully took place in 4-5 years into 6 - 12 months.
And you see no readily apparent disconnect between the hope to get the next one out sooner and the fact that you have not started yet?
On Thursday, 11 August 2016, Jeff Gilbert <email@example.com
I disagree. This sort of line-fitting estimation is naive, and ignores
too much in this case.
On Wed, Aug 10, 2016 at 4:23 AM, John Davis <firstname.lastname@example.org> wrote:
> Guys, Florian is making a really really good point.
> On Wednesday, August 10, 2016, Florian Bösch <email@example.com> wrote:
>> Sorry, typo, projected schedule should be:
>> GLES 3.1 release specification: 2014 (2 years ES 2.0)
>> WebGL 2.1 first draft specification: expected 2016 (???) (2 years ES 3.1,
>> 4 years WebGL 2.0, and counting)
>> WebGL 2.1 release specification: expected 2018 (???)
>> WebGL 2.1 public release: expected 2018 (???)