[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 500 for work on atomic renames?

From: <lsuvkne_at_onemodel.org>
Date: 2007-06-12 00:25:35 CEST

>>> On Mon, Jun 11, 2007 at 3:00 pm, kfogel@red-bean.com wrote:
>> $7500 for work on atomic renames?
>> <snip>
> I'm not sure whether the price is reasonable or not (haven't
> investigated closely enough), but I suspect that any contract would
> best be arranged in stages, with each stage having its own deliverable
> and price. For example:
> 1) Determine scope of remaining work.
> Deliverable: a post to dev@ describing what's left.
> 2) Propose design/implementation to finish off remaining work.
> Deliverable: a post to dev@, etc.
> 3) Shepherd proposal (2) through modification and acceptance.
> Deliverable: dev community consensus on the fix.
> 4) Implement it.
> Deliverable: a patch, also posted to dev@.

Very good points; I also now see this possibly-related issue, which I need to ponder:

Perhaps in this case, the example deliverable items 1-2 are largely done
(unless more big surprises are uncovered) with 3 perhaps partly done (or
fully, not sure) and some part of #4 done. I say that based on
reading links such as these and knowing there is some work in place on a separate branch already:
..with other info scattered across links contained in my earlier post

If there are no big surprises discovered beyond what was
described there, I wonder whether it might be possible to scope the
effort now. Surprises being the big wildcard, given the complex history
of this issue.

Also (though I guess this will be more applicable later on...), I would
like to think about #4 as being integration of a patch into trunk
(including tests written), after having had substantial code review and
any needed follow-up changes. That could leave scope feeling a bit
mushier as far as the work involved, but gets a lot closer to feeling
"done" as far as the actual need goes. The scope definition might be
tightened by carefully describing the tests, but again that's probably
something to discuss more later.

Thanks very much--any and all feedback on this is most welcome.

Sincere best regards,


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 12 00:26:09 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.