On Jan 28, 2005, at 10:25 AM, Steve Greenland wrote:
> On Fri, Jan 28, 2005 at 09:20:16AM -0500, Scott Palmer wrote:
>> My description was incomplete. A and B are being developed together
>> in
>> parallel. A method is added to A because it is immediately needed in
>> B, or a new code in B is added to accommodate for changes made in A
>> literally seconds earlier.
>
> Then they are not, in fact, seperate projects, and treating them as
> such
> is causing you pain.
>
> I understand that your intent is that they will, someday, be seperate,
> and the interface to A will stabilize. Why not wait for that day, and
> then move A outside of B, and set up externals then?
Yes, I think that is exactly what needs to happen. In fact I think I
will treat A along the lines of a Vendor Branch but in reverse.
Instead of incorporating new drops from outside vendors, I will be
exporting new drops of A from within the B project to it's own place in
the repository, where it will appear to be a much more stable entity.
The downside is that the developer working on A will now have a working
copy of B+A instead of the simpler A-only WC. Not really a big deal.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 28 17:12:44 2005