gnab/remark

Preparing for 0.15.0 release

Opened this issue · 6 comments

peterj commented

Hello everyone!

Since the last release of remark (v.0.14.0) was on Sep 15. 2016, I think it would be appropriate to cut a new release :)

I would like to use this issue to track any work that's needed in order to do the release (@gnab, it would be great if you take a quick look at it as well, just in case I've missed anything).

  • PR to master + merge
  • Create a new Github release from master with tag 0.15.0
  • Commit the new remark-0.15.0.min.js to gh-pages branch (downloads folder)
  • Write and update release notes (HISTORY.md) (PR: #609)
  • As part of the release notes update, we should also review the Wiki to make sure it's up-to-date with the features
  • Update the list of contributors (PR: #605)
  • Update index.html in gh-pages branch - update demo slideshow with new features

I've probably missed something, so please feel free to comment & add more to this.

dvberkel commented

Maybe update the list of contributors. We can get the names from the git log with the following command

 git log | grep Author | cut -d ' ' --fields=2- | cut -d '<' -f 1 | sort | uniq > contributors.txt

Something similar should be done with the wiki repository

  • 👍1
gnab commented

Looks good @peterj! I believe I used to also update the index.html in the gh-pages branch, and if there are any new features worth mentioning, the demo slideshow could be updated to present these in addition to the wiki being updated.

  • 👍1
peterj commented

I merged the master to develop to resolve a conflict (README only) and then merge develop back in to master. A new release on the master is created. I will work on committing new remark-0.15.0min.js to the gh-pages next and update the remaining items.

  • 👍1
datapolitan commented

I appreciate all the work @peterj and the rest of the team have done, but as a long-time user of Remark, the issue in #613 is really serious for us and I'd ask that if you're going to put out these large releases, you expand your testing to include GitHub Pages builds. I just found out about this and want to delve more into the code to figure out what happened. I'm happy to help contribute to the solution, but hope you'll also take this as a point of improvement for future releases.

peterj commented

@datapolitan thanks for responding, I completely missed the issues. I have reverted the .min back to 0.14.1 and I'll make sure we do more testing before switching it to latest.

  • 👍2
kud commented

Hello!

How to get this version on CDNs? :)

Cloudflare only suggests 0.14 for the moment.