Michael Koziarski wrote:
Is he alive? Does anyone know if he's OK?
Leon's fine. He's just overworked at the dayjob.
It would be good if he could still advise others on (i) where to look in
the code when diagnosing a problem, and (ii) the level of testing
required when submitting a patch + tests.
Do you know the figures here? Without daring to tread on the ground of
"is Rails enterprise-ready?" I would point out that being able to offer
functionality either through a Web UI or via a web service is a big
enterprise "tick in the box".
Well ActionPack's REST support is pretty complete at present.
That's good. Document/literal SOAP (as opposed to SOAP RPC) would be
another thing to have on the todo list.
But if
someone's able to start fixing the show stoppers like these, then we
can definitely continue to include it:
http://dev.rubyonrails.org/ticket/2553
http://dev.rubyonrails.org/ticket/3567
etc.
Personally, I believe that anything up to Rails 2.0 should respect the
commitment to "not break the Book (AWDR)". At the very least, there
should be a succession of versions that warn the user before something
actually breaks.
Perhaps you should go through the book and publish the "truck number"[1]
of each feature.
It's not really a question of 'truck numbers' (nice phrase though),
but rather that AWS is broken now, and noone has stepped up to the
plate to take over maintenance. I'd definitely prefer to continue to
include AWS in rails, at least until rails 2.0, but in it's current
state, it's just too broken.
Thanks - that puts the problem in a very different light from DHH's
post. Has there been any previous call for an AWS maintainer on this list?
If you're using AWS in production at present, please consider looking
into the tickets and providing fixes. That's the best way to ensure
that AWS stays in rails.
We are only using Rails for prototyping at present, and not using AWS...
regards
Justin
[1] Truck Number - the number of people who would need to be run over by
a truck to render a given feature unviable.
--
Cheers
Koz
thanks again
Justin
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
