search

asciidoctor / atom-language-asciidoc

⚛ AsciiDoc language package for the Atom editor.
https://atom.io/packages/language-asciidoc
MIT License
42 stars 20 forks source link

Release 1.4.0 !! #134

Closed ldez closed 8 years ago

ldez commented 8 years ago

Before doing auto-completion migration we must release.

Date Version Tests Assertions
2015-09-01 v0.12.0 29 92
2016-04-29 v1.0.0 82 (+53) 429 (+337)
2016-05-02 v1.1.0 178 (+96) 961 (+532)
2016-05-12 v1.2.0 238 (+60) 1374 (+413)
2016-05-20 v1.3.0 288 (+50) 1793 (+419)
2016-05-21 v1.4.0 320 (+32) 2126 (+333)

@nicorikken are you agree ?

nicorikken commented 8 years ago

I didn't dare to ask for a release yet, but glad you are going for it! 👍 (only 17hrs ago the previous was released 😄 ) I'm glad I took the time to review PR's and issues yesterday and today. Going forward I'll try to keep up, even though I might be off working on other parts of Asciidoctor.

ldez commented 8 years ago

Release time !! :tada: Again !! :tada: :beers:

https://github.com/asciidoctor/atom-language-asciidoc/releases/tag/v1.4.0

ldez commented 8 years ago

Next step the 2.0.0 release ?

nicorikken commented 8 years ago

can be what features would you opt for? (let's do some release planning 😛 ) I guess autocompletion copy, inline refactor, distinguishing block types, and matching normal paragraphs, all for better style naming?

ldez commented 8 years ago

Or simply autocompletion copy ? :smile:

ldez commented 8 years ago

Small steps, always small steps :smile:

ldez commented 8 years ago

I'm currently preparing the new release system... (related to #87)

mojavelinux commented 8 years ago

I agree with the small steps. Big releases were a bad habit I got into in core and they are very stressful. :+1: for reducing stress and automating.

Let's just use the milestone setting to do release planning for issues. That helps people who want to help know what to focus on (or they can make a request to have an issue included).