Windows Testing Force

[parkr]

WTF – Windows Testing Force. This team will be mentionable via @jekyll/windows and will be diligently used to avoid breaking future releases.

If you would like to join, please comment below and I will add you. Being a part of this team means we'll be asking you to test future builds of Jekyll. You must know how to run Jekyll based on a the master branch of this repo or based on pull requests in this repo and have the time to test a potential new build within a 48 hour window. If you need help with git apply-ing a .patch from a PR, just holler and someone will come to your aid.

[XhmikosR]

/me is in

lol at the WTF :P

[juthilo]

Hi! Glad to be part of the WTF. (I promise it's not just because of the name.) 😄

[pinceladasdaweb]

Me too.

[parkr]

Thanks so much guys!

[maiertech]

I wonder if it would make sense to explore other options to run Jekyll on Windows. For instance, create a Jekyll Docker image. I'm using Jekyll on Windows at work, but every couple of weeks something breaks and sometimes it's a time sink to figure out the culprit. Ruby on Windows is also less than ideal, even with Chocolatey. I'm thinking more and more that it's worth trying to put Jekyll in a sandbox, even though this comes with some overhead, too.

[alfredxing]

I'm in as well. I'm mainly on OS X nowadays but I do use Windows occasionally.

[XhmikosR]

Personally, I still think we should try setting up AppVeyor for the tests. CI will always beat manual testing.

[troyswanson]

@mdotasia https://registry.hub.docker.com/u/troyswanson/jekyll/

[parkr]

Closing, but anyone else who wants to join, just holler!