Milestones
List view
- upgrade to Rails 5.1 - fix remaining issues
Due by March 31, 2018•11/11 issues closed- Due by February 29, 2016•2/2 issues closed
- Due by December 30, 2015•9/9 issues closed
bug fixes + small features
Due by August 17, 2014•11/11 issues closed- Due by June 22, 2014•3/3 issues closed
- No due date•3/3 issues closed
- Due by April 5, 2014•15/15 issues closed
Hopefully, the last version before the 3.0
Due by November 30, 2013•12/12 issues closed- Due by September 30, 2013•13/13 issues closed
More explanation here: http://www.locomotivecms.com/articles/spring-2014-roadmap
Due by December 31, 2014•42/42 issues closed- Due by June 30, 2013•18/18 issues closed
- No due date•1/1 issues closed
Fixes and security patches for the 1.0 release.
No due date•1/1 issues closed- Due by May 31, 2013•55/55 issues closed
The engine can no longer be used standalone, only as a mountable engine and now runs on rails 3.1 or greater. The entire engine will be namespaced to prevent naming collisions within applications including the engine. The administration backend will use backboneJS to allow content to be updated asynchronously.
No due date•2/2 issues closedi18n specific content will be supported. There will be a standard API which will allow exporting and importing of data to replace the current system. This will also allow addons to access data from locomotive in a standardized way.
Due by March 31, 2012•99/99 issues closedThe current version of Locomotive seems pretty stable so it's time to tag it. Moreover, there are 2 big features almost done which may break a lot of things in Locomotive.
Due by September 30, 2011•5/5 issues closed