# Issues we MUST resolve before 1.0 release \[6 remaining\]

**URL:** <https://talk.commonmark.org/t/issues-we-must-resolve-before-1-0-release-6-remaining/1287>\
**Category:** Spec\
**Tags:** release-1.0\
**Created:** [July 26, 2015, 12:26am UTC](https://talk.commonmark.org/t/issues-we-must-resolve-before-1-0-release-6-remaining/1287 "2015-07-26T00:26:38Z")\
**Posts on this page:** 1\
**Showing post:** 54

<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:** [April 11, 2019, 12:31am UTC](https://talk.commonmark.org/t/issues-we-must-resolve-before-1-0-release-6-remaining/1287/54 "2019-04-11T00:31:43Z")

</div>

> @jgm @codinghorror would it make more sense to  
> maintain this list in one and only one place, i.e.  
> GitHub? Maybe create `1.0 minimum` and `1.0 should`  
> milestones (or labels). Issues can always be moved  
> to earlier milestones as desired.

That would make a lot of sense, I agree.

---

_[View the full topic](https://talk.commonmark.org/t/issues-we-must-resolve-before-1-0-release-6-remaining/1287)._