Ok, I hope upgrading jekyll on ubuntu is easy. I’ve tried a couple of times and quickly got mired in incompatible versions ruby.
> On Apr 17, 2016, at 2:30 PM, Josh Elser <[email protected]> wrote: > > In case you missed CALCITE-1202: > > tl;dr `cd site; rm Gemfile.lock; bundle install` the next time you want to > update the website. > > I was a little cavalier in making this update because of the potential > variance for developers who want to edit the website. This will bring us all > on the same page and, hopefully, make updating the website less scary :) > > I did make a pass over the website to make sure the update from jekyll 2 to > jekyll 3 didn't break anything, but did not find any issues. If you see > something wrong, feel free to send a note and I'll try to look into it! > > -------- Original Message -------- > Subject: [jira] [Resolved] (CALCITE-1202) Lock version of Jekyll used by > website > Date: Sun, 17 Apr 2016 21:13:25 +0000 (UTC) > From: Josh Elser (JIRA) <[email protected]> > Reply-To: [email protected] > To: [email protected] > > > [ > https://issues.apache.org/jira/browse/CALCITE-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Josh Elser resolved CALCITE-1202. > --------------------------------- > Resolution: Fixed > > Fixed in > https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=b66d414661926afdb82aea71432fa18022a666e2 > >> Lock version of Jekyll used by website >> -------------------------------------- >> >> Key: CALCITE-1202 >> URL: https://issues.apache.org/jira/browse/CALCITE-1202 >> Project: Calcite >> Issue Type: Improvement >> Reporter: Josh Elser >> Assignee: Josh Elser >> Priority: Trivial >> Fix For: 1.8.0, avatica-1.8.0 >> >> >> I had a newer version of Jekyll installed for other projects and realized >> that this was causing a significant amount of changes in the generated HTML. >> We should lock jekyll-2.4.0 as the version we want to use in the Gemfile. >> This will prevent unintended changes to HTML due to the installed version of >> Jekyll being potentially different across different developer machines. >> Presently, this is being set by the github-pages gem implicitly. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332)
