# Fast away the old year passes

**URL:** <https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328>\
**Category:** Meta\
**Created:** [January 17, 2017, 2:27am UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328 "2017-01-17T02:27:56Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![jkdev](https://cdn.commonmark.org/letter_avatar_proxy/v2/letter/j/e79b87/32.png) [@jkdev](https://talk.commonmark.org/u/jkdev)\
**Post date:** [January 17, 2017, 2:27am UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/1 "2017-01-17T02:27:56Z")

</div>

Seems our homepage’s last paragraph is in need of a chronological update.

> # When is the spec final?
> 
> The current version of the CommonMark spec is complete, and quite robust after a year of public feedback … but not quite final.
> 
> With your help, we plan to announce a finalized 1.0 spec and test suite in early 2016.
> 
> \<3

[http://commonmark.org](http://commonmark.org) (Accessed January 16, 2017)

---

<div class="post-metadata">

**Author:** ![codinghorror](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/codinghorror/32/2_2.png) [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Post date:** [January 27, 2017, 12:39am UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/2 "2017-01-27T00:39:50Z")

</div>

Yes that’s true cc @jgm 😉

---

<div class="post-metadata">

**Author:** ![jgm](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/jgm/32/1360_2.png) [@jgm](https://talk.commonmark.org/u/jgm)\
**Post date:** [January 27, 2017, 5:22pm UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/3 "2017-01-27T17:22:58Z")

</div>

The task was more difficult than we knew then, and my time has been limited. We’ve made lots of progress on the spec, we have some very high-quality implementations that are getting good use (including in industry), and hopefully we’re converging on something that could be called 1.0.

(Anyway, I take no responsibility for the wording that you quote: that was all @codinghorror!)

---

<div class="post-metadata">

**Author:** ![codinghorror](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/codinghorror/32/2_2.png) [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Post date:** [March 5, 2017, 7:01am UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/4 "2017-03-05T07:01:45Z")

</div>

OK! I’ve updated the website to say 2017. Let me know if we should change it to 2018 or later @jgm.

---

<div class="post-metadata">

**Author:** ![edward.brey](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/edward.brey/32/1521_2.png) [@edward.brey](https://talk.commonmark.org/u/edward.brey)\
**Post date:** [February 27, 2019, 2:49pm UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/5 "2019-02-27T14:49:45Z")

</div>

It’s that time of year again. 🙂 The home page still predicts, “we plan to announce a finalized 1.0 spec and test suite in 2018.”

---

<div class="post-metadata">

**Author:** ![codinghorror](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/codinghorror/32/2_2.png) [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Post date:** [March 25, 2019, 2:56am UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/6 "2019-03-25T02:56:28Z")

</div>

All updated now, thanks @edward.brey

---

<div class="post-metadata">

**Author:** ![Fabio](https://cdn.commonmark.org/letter_avatar_proxy/v2/letter/f/f4b2a3/32.png) [@Fabio](https://talk.commonmark.org/u/Fabio)\
**Post date:** [March 3, 2020, 2:45pm UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/7 "2020-03-03T14:45:07Z")

</div>

Another year has passed…

Considering that the original version of that sentence talked about “early 2016”, maybe there should be no indication of an ETA. But I’ll leave that to you.

---

<div class="post-metadata">

**Author:** ![jgm](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/jgm/32/1360_2.png) [@jgm](https://talk.commonmark.org/u/jgm)\
**Post date:** [March 3, 2020, 5:02pm UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/8 "2020-03-03T17:02:52Z")

</div>

I would suggest that instead of an ETA, the front page should  
cite some accomplishments. E.g., implementations in N languages,  
adoption of (extended) commonmark by GitHub, GitLab, Swift,  
Qt, reddit (with some transitional compatibility quirks),  
Discourse.

But I don’t control that page, @codinghorror does.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/codinghorror/32/2_2.png) [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Post date:** [March 15, 2020, 7:58pm UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/9 "2020-03-15T19:58:47Z")

</div>

Sure, I’ll edit that soon. We have a lot of downtime now.. 🦠

---

<div class="post-metadata">

**Author:** ![codinghorror](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/codinghorror/32/2_2.png) [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Post date:** [March 26, 2020, 7:59am UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/10 "2020-03-26T07:59:36Z")

</div>

OK! I’ve edited the page at [https://commonmark.org/](https://commonmark.org/) – scroll to the bottom and see what you think @jgm

> The current version of the CommonMark spec is quite robust after many years of public feedback.
> 
> There are currently CommonMark implementations for [dozens of programming languages](https://github.com/commonmark/commonmark-spec/wiki/List-of-CommonMark-Implementations), and the following sites and projects have adopted CommonMark:
> 
> - GitHub
> - GitLab
> - Swift
> - Qt
> - Reddit
> - Discourse

I figure it’s best to get rid of version promises and years. Anything else I should add? Stay safe, everyone. 🙏

---

<div class="post-metadata">

**Author:** ![peter-fb](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/peter-fb/32/2083_2.png) [@peter-fb](https://talk.commonmark.org/u/peter-fb)\
**Post date:** [June 25, 2020, 7:09am UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/11 "2020-06-25T07:09:18Z")

</div>

@codinghorror Stack Overflow and all other Stack Exchange websites [switched to CommonMark](https://meta.stackexchange.com/questions/348746/were-switching-to-commonmark?cb=1) a few days ago.

That’s huge, you might want to add that. 🙂

---

<div class="post-metadata">

**Author:** ![codinghorror](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/codinghorror/32/2_2.png) [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Post date:** [June 28, 2020, 5:28pm UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/12 "2020-06-28T17:28:18Z")

</div>

That is fantastic news! 🎉 I’ve updated the website and put the `<ul>` into alphabetic order by site.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/codinghorror/32/2_2.png) [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Post date:** [March 29, 2022, 8:26pm UTC](https://talk.commonmark.org/t/fast-away-the-old-year-passes/2328/13 "2022-03-29T20:26:54Z")

</div>

More good news:

> **[Compose with Markdown in Google Docs on web](https://workspaceupdates.googleblog.com/2022/03/compose-with-markdown-in-google-docs-on.html)**
>
> What’s changing  In Google Docs, you can now select “Automatically detect Markdown” from Tools \> Preferences to enable auto correcting for M...

Google Docs now supports Markdown!
