When do you think we'll ship 1.0 of the CommonMark spec?

release-1.0

#1

From my observation, the community here has rightly been focused on the concrete remaining blockers for a v1.0 of the CommonMark spec, via Issues we MUST resolve before 1.0 release [8 remaining] and related topics.

Rather than pollute that healthy focus, I wanted to start a separate topic to gauge the intuition of the various experts and community members here who have been working on this. This topic is here to also explicitly invite you to lean on the thinking fast, system 1 part of your brains.

I’ll update this post periodically with a new poll so we can capture the different collective sentiments at different points in time alongside each other. Feel free to elaborate on your answers in the comments below.

I’ll keep each poll open for 2 weeks.

When do you think we’ll ship 1.0 of the CommonMark spec?

Just, take your best guess; think fast and slow.

Sat April 28 - Sat May 12, 2018

  • Within the next 3 months
  • Between 3 and 6 months from now
  • Between 6 and 12 months from now
  • More than 1 year from now

0 voters


#2

It’s entirely up to @jgm so I think there’s only one person we need to ask.


#3

If some form of consensus is reached here, could this quote from the front page be updated? “we plan to announce a finalized 1.0 spec and test suite in 2017”


#4

I went ahead and posted a PR to the website bumping the anticipated release: https://github.com/commonmark/web/pull/18


#5

As time goes on, and the standardization effort loses steam, does it make any sense to make some concessions and just call it done, or make best-effort decisions on the remaining blockers, for the sake of signalling?

It’s been a while, and there are a number of implementations, and having a release would bring some excitement and long-awaiting closure to a major issue in the programming community.

Presumably there can be a CommonMark 1.1 if development steam picks up, which it well could after a big release.