zzak · April 21, 2016 09:42 · Apr 21, 2016
diff --git a/sinatra-two-point-oh.md b/sinatra-two-point-oh.md
@@ -0,0 +1,27 @@
+This is a gist to track the feature development for Sinatra 2.0.
+
+## Where can I find the latest changes?
+
+Keep an eye on the [CHANGELOG](https://github.com/sinatra/sinatra/blob/master/CHANGELOG.md) which is updated as features and bug fixes land. We generally try to keep this limited to "major" changes to cut down on cruft.
+
+## Is there a roadmap?
+
+At the moment, there's a [milestone for 2.0.0](https://github.com/sinatra/sinatra/milestones/2.0.0) on the issue tracker. But we'll try to land as many [features](https://github.com/sinatra/sinatra/labels/feature) as we can in the next release. No promises.
+
+## What's the biggest change?
+
+As I mentioned in the blog post regarding [Sinatra 2.0](http://zzak.io/log/2016-04-18-the-road-to-sinatra-2.0.html), the largest changes are just dropping support for older versions of Ruby and Rack.
+
+Although using [Mustermann](https://github.com/rkh/mustermann) the new default routing engine is probably the second biggest change, it's mostly an internal.
+
+## What's new in Rack 2.0?
+
+This is something that isn't exactly documented, although [@tenderlove](https://twitter.com/tenderlove) has spoke a few times about his changes to the [Rack request and response API](https://www.youtube.com/watch?v=1EeWXojdqvU).
+
+There have been a few changes internally to Sinatra in order to support the latest version of Rack, but otherwise we are testing against [Rack master](https://github.com/sinatra/sinatra/blob/38f0cb9/Gemfile#L14) so any breaking changes should be caught by CI.
+
+With that said, I (too) would love to see the latest changes in Rack 2.0 documented :)
+
+
+
+