On 7-feb-2006, at 12:31, Steve Purcell wrote:
On Tuesday 07 February 2006 08:04, Kevin Clark wrote:
Whatever. I'm disillusioned.
I'd love to get this stuff fixed, but rails-core doesn't seem to
scale
with regards to handling patches.
I'm sorry if I sound ungrateful. I'm really not. I'm just tired of
not
being able to fix things.
It's not clear to me whether the bottleneck is the time the core
developers
have available for reviewing patches, or simply the time required
to merge
acceptable patches.
If the latter is the problem, as I suspect it is, perhaps the core
team
would be willing to solicit one or more non-core volunteers to act as
"merge monkeys". The volunteers' task would be to fix up, apply
and close
patches signed off in principle by the core team.
Any thoughts?
Which would include giving the "monkeys" complete access to the 37s
application code (because I think THIS is what all the patches get
tested against, I think). The problem is that there are tests which
are not included in Rails and are effectively proprietary, but 37s
(being the core maintainers of the framework) have the privilege of
verifying patches against their own applications before the patches
are rolled out.
Not to offend anyone - just a thought.
--
Julian 'Julik' Tarkhanov
me at julik.nl
_______________________________________________
Rails-core mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-core
