New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preparing for 0.15.0 release #602
Comments
|
Maybe update the list of contributors. We can get the names from the git log with the following command Something similar should be done with the wiki repository |
|
Looks good @peterj! I believe I used to also update the |
|
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 |
|
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. |
|
@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. |
|
Hello! How to get this version on CDNs? :) Cloudflare only suggests 0.14 for the moment. |
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).
gh-pagesbranch (downloadsfolder)HISTORY.md) (PR: #609)index.htmlingh-pagesbranch - update demo slideshow with new featuresI've probably missed something, so please feel free to comment & add more to this.
The text was updated successfully, but these errors were encountered: