Re: Schedule for next release: Asciidoctor 0.1.1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Schedule for next release: Asciidoctor 0.1.1

mojavelinux
Administrator
I vote yes for cutting a 0.1.1 release.

Jason and Ryan?

-Dan

On Sun, Feb 17, 2013 at 2:05 PM, Dan Allen <[hidden email]> wrote:
We are just about ready for the Asciidoctor 0.1.1 release. You can track the release progress in the issue tracker:


Each open issues has a pull request pending, in addition to a few extra pull requests. As soon as those are all merged in, I'm recommending that we tag 0.1.1 (Monday or Tuesday).

I'll share a more detailed changelog when we announce the release. Off the top of my head, the big change that 0.1.1 introduces is that it processes all the markup in one pass, whereas previously it was evaluating the preprocessor directives (ifdef, include and attribute entries) on a first pass, then going back and parsing all the other markup (see issue #143 [1]). This split was causing processing directives to be evaluated differently than in AsciiDoc. That's now resolved.

We've also been working on a default stylesheet for Asciidoctor. That's planned for 0.1.2, which you can track here:


-Dan

[1] https://github.com/asciidoctor/asciidoctor/issues/143

--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597




--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

Reply | Threaded
Open this post in threaded view
|

Re: Schedule for next release: Asciidoctor 0.1.1

LightGuardjp
+1 Let's release. Once that hits rubygems I'll update the maven plugin.


On Wed, Feb 20, 2013 at 1:04 PM, mojavelinux [via Asciidoctor :: Discussion] <[hidden email]> wrote:
I vote yes for cutting a 0.1.1 release.

Jason and Ryan?

-Dan


On Sun, Feb 17, 2013 at 2:05 PM, Dan Allen <[hidden email]> wrote:
We are just about ready for the Asciidoctor 0.1.1 release. You can track the release progress in the issue tracker:


Each open issues has a pull request pending, in addition to a few extra pull requests. As soon as those are all merged in, I'm recommending that we tag 0.1.1 (Monday or Tuesday).

I'll share a more detailed changelog when we announce the release. Off the top of my head, the big change that 0.1.1 introduces is that it processes all the markup in one pass, whereas previously it was evaluating the preprocessor directives (ifdef, include and attribute entries) on a first pass, then going back and parsing all the other markup (see issue #143 [1]). This split was causing processing directives to be evaluated differently than in AsciiDoc. That's now resolved.

We've also been working on a default stylesheet for Asciidoctor. That's planned for 0.1.2, which you can track here:


-Dan

[1] https://github.com/asciidoctor/asciidoctor/issues/143

--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597




--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597




If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Re-Schedule-for-next-release-Asciidoctor-0-1-1-tp9.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--