mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pat Ferrel <>
Subject Re: Website Incident
Date Sat, 13 May 2017 16:33:42 GMT
+1, headline: "A serendipitous mistake leads to fast action at Mahout”

We now know Trevor is a webdev god :-)

On May 13, 2017, at 8:21 AM, Andrew Musselman <> wrote:

Trevor, thanks for the late night repairing things; I'm a +1 and will scrub
this weekend for any markdown issues.

On Sat, May 13, 2017 at 12:40 AM Trevor Grant <>

> We had a little incident tonight where the 'beta' website was accidentally
> made "live".
> There was a decision point where we could either attempt to roll back the
> subversion commit, or rebuild the old website, with the original website
> "skin", and push that into subversion.  It was a bit of a panic moment, the
> way to revert in svn wasn't clear, the way to rebuild via jekyll with the
> old skin was.
> If you look at the site at the moment ( it may
> look a very slight touch "off" wrt layout due to how Jekyll compiles
> markdown vs how the old CMS perl scripts did.
> What this means to any committers interested in updating the website-
> 1. CMS (the old website content management system) is effectively out of
> service for the moment. Any edits made via this will likely yield no
> effect, if even possible at all.
> 2. Mahout 1984 has a file that contains how to "push" the new website
> 3. The 0.13.1-SNAPSHOT website docs AND 0.13.1 Scala/Java Docs are also now
> live. (this is the silver lining of the incident- though they are based on
> the current "dorky" layout)
> Calling for 72 hour, lazy consensus on making this change over permanent
> (as opposed to someone doing some research on figuring out how to get into
> svn and roll back to old site; +1 = let it be, -1 do a revision in svn)
> Following that period, assuming no objections- will file JIRA and begin
> work on updating Jenkins to automatically build and push the site nightly
> with any changes to docs (which will happen via gihub pull request- atm
> current site can be updated via changes to
> changes to docs can be made by prs against files in

View raw message