Re: Trouble forking my project
Re: Trouble forking my project
- Subject: Re: Trouble forking my project
- From: Graham Cox <email@hidden>
- Date: Thu, 25 Mar 2010 10:35:29 +1100
On 24/03/2010, at 5:05 PM, Eli Bach wrote:
> I can only suggest with the utmost conviction that you actually fork the code base, [as in, have completely separate 'bug fix' and 'radical change' branches]. Either your radical changes will leak into your bug fix version, or you won't be able to do some change because it will get too complicated to do while maintaining the bug fix version.
>
> And if you don't have your code in a version control system that supports branching [and no, CVS does NOT count], you go to your bedroom and think about that while I go and make a switch to punish you with. If you're a one or two-man shop, you can use Perforce for free [with free cli and gui tools to go with the server], and Subversion has gotten better at tracking/merging branches, and the youngun's have a hankerin for git...
>
> Eli
>
Thanks Eli (and Mike too, who voiced much the same opinion). I guess the term 'fork' in my title was a bit misleading. The change isn't that radical. Basically I want to add a major new feature but in the meantime make it possible to release bugfixes if necessary before that new feature is ready to go. Any bugfixes also need to apply to the new version as well, so a complete fork is probably not appropriate.
However, in general I agree with you. I'm using Subversion.
--Graham_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden