Thanks Rick,

>From my reading of that schedule we could hope to have ES6 features
like modules and classes ready for use in production code (via
something like traceur) by Q1 next year?
The June/July/Dec 2014 dates are simply dot the i's and cross the t's
milestones, standardisation bureaucracy?

In other words we won't have significant changes to the language and
we can finally start to integrate ES6 into production codebases?

On Fri, Nov 1, 2013 at 1:23 PM, Rick Waldron <waldron.rick at gmail.com> wrote:
>
>
> On Fri, Nov 1, 2013 at 12:02 AM, Nathan Wall <nathan.wall at live.com> wrote:
>>
>> Hey guys, I really think you're all doing an awesome job with the
>> development of the future of the language, especially all the work Allen's
>> putting into the drafts.  I'm really dying to start using some of these
>> features.
>>
>> Last I heard (probably over a year ago), the plan was to have ES6 out by
>> the end of this year...  It still looks like there's a good bit of work to
>> be done for things to be finalized.  Are there any updates on when we can
>> hope to have a finalized ES6?
>>
>
> Schedule:
> https://github.com/rwaldron/tc39-notes/blob/48c5d285bf8bf0c4e6e8bb0c02a7c840c01cd2ff/es6/2013-03/mar-13.md#416-current-status-of-es6
>
>
>>
>> Nathan
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>
>
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>

Thanks Rick,

From my reading of that schedule we could hope to have ES6 features like modules and classes ready for use in production code (via something like traceur) by Q1 next year? The June/July/Dec 2014 dates are simply dot the i's and cross the t's milestones, standardisation bureaucracy?

In other words we won't have significant changes to the language and
we can finally start to integrate ES6 into production codebases?