I was made aware of a security issue with OctoPrint 1.2.0 and 1.2.1 a couple of hours ago. I just fixed that and pushed a new release 1.2.2. The changelog is here: https://github.com/foosel/OctoPrint/releases/tag/1.2.2

I just tagged and pushed 1.2.1 to the master branch. It includes some minor bug fixes of things that were reported to me since the 1.2.0 release.

It has come to my attention that apparently the last release of OctoPi 0.11.0 from February (the one that introduced RPi2 compatibility and which is based on the Raspbian release from 2015-01-31) contains a little issue with the shipped OctoPrint checkout that prevents updates of OctoPrint on this image to run smoothly.

The day has finally arrived, I'm declaring 1.2.0 as stable :) Just pushed and tagged 1.2.0 on the master branch, no "-RC" postfix on this one ;)

I just tagged and pushed another Release Candidate of 1.2.0 to the master branch on Github, 1.2.0-RC3.

Since there were some minor issues reported with the RC1 (concerning backwards compatibility to older versions of setuptools and pip that are still present on a large number of systems out there) I fixed those and just tagged RC2.

I just tagged and pushed 1.2.0-rc1 to the master branch. This is the first release candidate of the 1.2.0 release that's been in the works for the last couple of months.

My initial plan was to put out a Release Candidate for 1.2.0 in May. I might still be able to, but sadly a real life bug has forced me to keep my feet still for this week, so I'm not sure.

It's not a secret that OctoPrint so far lacked support for Makerbot printers and their clones (e.g. Flashforge) and that I wasn't going to do anything about that due to various reasons (the most prominent one being no access to a machine to test with, but admittedly also some other reservations). With the arrival of the plugin system in OctoPrint's development branch +Mark Walker took it upon himself to change that and with "GPX" [1] developed a plugin around the "gpx" tool, which converts GCODE to the x3g format used by these printers. Mark has the plugin do this on the fly, basically having it act as a translation layer between OctoPrint itself and the serial port connected to the printer and thus allowing FlashForge and Makerbot printers up until Gen5 (read: Replicator 2 being the last one) to work together with OctoPrint.

While I'm currently fully focused on getting 1.2.0 (aka the devel branch) release ready and out of the door as soon as possible, I nevertheless just pushed a new release of the master branch.