If you were launching a site in late September, would you be
developing with Rails 1.1 or on edge rails?
Joe
Joe Van D. wrote:
If you were launching a site in late September, would you be
developing with Rails 1.1 or on edge rails?
1.1.3 is a safe bet, but edge isn’t that big of a risk. Edge tends to
stay pretty stable, since there is reasonably good test coverage.
Probably you should find a revision of edge that seems stable for you
and stick with that. If you have good functional tests for your app,
seeing if you can run on a new revision of Rails shouldn’t be that hard.
–
Josh S.
http://blog.hasmanythrough.com
On 6/27/06, Josh S. [email protected] wrote:
Joe Van D. wrote:
If you were launching a site in late September, would you be
developing with Rails 1.1 or on edge rails?1.1.3 is a safe bet, but edge isn’t that big of a risk. Edge tends to
stay pretty stable, since there is reasonably good test coverage.
Probably you should find a revision of edge that seems stable for you
and stick with that. If you have good functional tests for your app,
seeing if you can run on a new revision of Rails shouldn’t be that hard.
I do have fairly decent tests, but I’m worried about stuff like memory
leaks, security issues, and so forth.
You mean 1.1.2? Didn’t know about 1.1.3.
On Tue Jun 27, 2006 at 11:38:49AM -0700, Joe Van D. wrote:
On 6/27/06, Josh S. [email protected] wrote:
Joe Van D. wrote:
If you were launching a site in late September, would you be
developing with Rails 1.1 or on edge rails?1.1.3 is a safe bet, but edge isn’t that big of a risk. Edge tends to
stay pretty stable, since there is reasonably good test coverage.
Probably you should find a revision of edge that seems stable for you
and stick with that.
routes are about 20% broken for me in edge. stuff using *prefix and
regex constraints. since i lke pretty urls and am too busy to dive into
the code and figure out whats up, it was reason enough to go back to the
‘gem’ version. YMMV