Roadmap to 3.0.0

[Galadirith]

2.0.1 (2015-09-06)

Place anything that is not a bugfix/critical in 2.1.0 :D

• Version 2.0.0: headings no longer work #88: ATX headers require a space.
• Update math.md with stricter syntax.
• Add empty env argument to markdownIt.parse()
• Correct instantiation conditions for markdown-it #92: Correct instantiation of markdown-it.

2.1.0 (2015-09-09)

• Fix deserialization due to not passing domFragment #107 Fix Dom Fragment Serialization
• Remove dependencies which need to be built. #94 Fix installation issues/Refactoring imageWatcher. Fixes also Clear Caches/Watchers upon closing a preview #52
• Diff algorithm is not working for changing OL start #98 Fix diff algorithm for <ol start="1">...</ol>

2.2.0 (2015-09-27)

• Copy rendered equations when invoking copyHtml() #55 Copy equations when invoking copyHtml()
• Create PR for markdown-pdf #56 PR to markdown-pdf (Support convertion to PDF for markdown-preview-plus travs/markdown-pdf#88)
• Add specs for update preview diff algorithm #58 Add update preview diff algorithm specs
• Add MathJax as explicit dependency #113 Migrate to MathJax dependency 2.4.0-electron.0.2.0

2.3.0 (2015-11-15)

@leipert

• Pandoc PDF rendering #57 Pandoc PDF rendering
• Extract specs from atom/markdown-preview-plus issues #85 Specs derived from markdown-preview issues
• Support pandoc standalone/TOC and toc switches. #102 Support Pandoc --standalone and --toc

@Galadirith

In this release I'm mainly focusing on style issues and enhancements.

• [WIP] Open text editor for relative links to files #73 Open relative links (PR towards Open relative links to files from markdown preview #72)
• In preview, README.md is autolinked to someone's README.md on Github #139 Add option to configure markdown-it linkify option.
• Merge upstream style enhancements from Themed Markdown Preview atom/markdown-preview#298
• Save as HTML can't do GitHub Style #112 Ensure consistent styling across preview and Save as HTML
• Add Syntax Theme Dropdown #115 Syntax theme dropdown/customisation
• I can't read my code because of the colors #123 Theme makes code unreadable (may be fixed by Themed Markdown Preview atom/markdown-preview#298)

2.4.0 (2015-11-29)

@leipert

@Galadirith

In this release I want to focus on enhancing our on-demand/auto source-preview sync features.

• On-demand/auto sync for markdown-it backend #9 Add auto sync of source-preview for markdown-it backend.
• Improve on-demand sync feedback (I don't like the red box even though I added it 😄).
• Sync preview with source position for pandoc backend #106 Investigate sync for Pandoc backend (I do not yet know if implementing will be possible).

2.5.0 (2015-12-13)

@leipert

@Galadirith

• Sync preview window with active Markdown file #137 Make preview active pane item when associated editor is made active pane item.

Compiling everything through to 3.0.0 into one issue may end up bloating this issue. If that happens we can split it up but for now we'll work with just the one.

[Galadirith]

@leipert I think we're looking good for 2.0.1. As long as there was no other bug fixes you had locally I'll go ahead and publish :D

[leipert]

@Galadirith Go for it, I will update the Changelog once you pushed.

[Galadirith]

Fantastic :D Its now out in the wild.

[Galadirith]

@leipert thanks for merging #101. I'll wait until 2100 GMT for any late bug reports and then publish 2.0.2 :D

[leipert]

@Galadirith I somewhat wanted to speedup the release schedule of 2.1.0. I hope that is okay with you, I finally want to see these installation bugs gone.

[Galadirith]

@leipert Yep no problem those changes to the milestones are all perfectly reasonable. I went to bed dreaming of ways to fix the ordered list issue #98 and I still was unsure about if it could be done by tomorrow. But I awoke with a rather uninteresting but simple solution, so rolling that out should hopefully be fine :D

[leipert]

@Galadirith Nice! Looking forward 👍

[Galadirith]

Fantastic, well everything's in master now and passing (shame about the shield.io badges but it looks like their changing servers). I'll give it a cooling off period for the day and then publish 2.1.0 in the evening. Thanks @leipert :D

[leipert]

@Galadirith Seems like the badges are working. Everything's a go then! I will try to publish it now, because I think I should able to publish as I am a contributor to the package.

[leipert]

@Galadirith It's in the wild!

[Galadirith]

@leipert Great :D 🎉 🎈 And its really good to know you were able to publish as a contributor, I was never sure about the division of permission between Github and Atom's package repository :D Great

[Galadirith]

@leipert I hope its ok, I did rebuild the aborted [ci skip] b578af3 commit on wercker simply because it was the commit reflected in the badge for anyone now grabing 2.1.0 and passing looks better than aborted :D

[leipert]

Yeah. We need a thing in the future that changes the README before publish to show the build status for a fixed tag or commit, so that it reflects the status of the package and not of the master branch.

But that is something reaaaaaaaaaaally unimportant 💃

[Galadirith]

But that is something reaaaaaaaaaaally unimportant 💃

Definitely :D

I've updated 2.2.0 with a milestone target set for a couple of weeks from now :D

[Galadirith]

@leipert I'm really sorry I've been missing for the last 2 weeks, the first month of my PhD has been busy. I really hope your Thesis completion went we'll.

I've fleshed out the next few releases with dates and issues to attack. I might still need to add some more or move things around, but thats always the case. Please do update with any issues you want to handle, and hopefully we can get back to some consistent releases. Thanks @leipert 😄

[Galadirith]

Sorry everyone I have to bump the candidate release dates by a week.

[Galadirith]

I really apologise again to everyone waiting for the next release of MPP. I have had to move development back again due to PhD commitments.

[leipert]

@lierdakil Do you think this roadmap is still relevant?

[lierdakil]

Honestly, I have no idea. There's so much legacy here I was honestly tempted to just close all issues and start from a blank slate... it takes a while to figure out if a particular bug was fixed at some point or not. Feel free to close since there's not much active development happening anyways.

[leipert]

As already mentioned in #269, I will gladly help to start organizing issues.

[lierdakil]

Using milestones for this now.