# Engines and current edge rails

**URL:** <https://www.ruby-forum.com/t/engines-and-current-edge-rails/93280>\
**Category:** Engines\
**Created:** [April 30, 2007, 12:21pm UTC](https://www.ruby-forum.com/t/engines-and-current-edge-rails/93280 "2007-04-30T12:21:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidstokar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/4da419/32.png) [@davidstokar](https://www.ruby-forum.com/u/davidstokar)\
**Post date:** [April 30, 2007, 12:21pm UTC](https://www.ruby-forum.com/t/engines-and-current-edge-rails/93280/1 "2007-04-30T12:21:42Z")

</div>

Hi there,

We’re using engines heavily in our current app - problem is that we’ve  
seen the lovely patch DHH just committed to edge rails to allow easy  
namespacing of routes (  
[http://railstips.org/2007/4/28/namespaces-added-to-routes](http://railstips.org/2007/4/28/namespaces-added-to-routes) ). We’d really  
like to move to edge to take advantage of this but we’re so heavily  
dependant on the current release of engines that we can’t afford to  
break that.

So - anyone know of any issues with edge rails and the current stable  
release of engines? Would we have to move over to an edge version of  
engines as well?

Cheers,

David