Ok, I get it now. But still, the most efficient way would be that the people with the most experience in a given area, would be the ones to maintain it. You are putting a restriction on scedule that does not apply here. Within a time-frame that is smaller than what an experienced person has available, than you are right. But as you said, web2py does not have a formal release-cycle, and there is currently no incentive in existance for defining one. So, in otherewprds, your example is correct, only when applied to a scheduled-project, which web2py clearly is not, by your standards. So in that case, experienced person B would be most suited for doing both assignments. The overall community-time invested would be only 4 hours. It may take longer to complete scedule-wise, but that has no relevance to an un-scheduled project. It may take massimo even a few months to get to that, for all I care, it would still remain more efficient.
-- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
