[Adium-devl] Changes in a branch

Colin Barrett timber at lava.net
Tue Oct 31 17:54:19 UTC 2006


I agree with this policy -- I would also like to point out svn1.5  
(which has greatly improved merge support). When it comes out, it  
would be excellent if we could upgrade our repo (and all our clients,  
of course) to svn1.5.

Also, reading up on branch management, merging, and distributed scms  
is a good idea. The darcs, arch, svk, and bazaar documentation are all  
excellent reading.

Oh, and about that Get Info window -- work on that will start after I  
finish these scroll bar improvements. So, next week (hopefully)?

-Colin


On Oct 31, 2006, at 7:48 AM, Christopher Forsythe wrote:

> So we've basically been doing it already, but I'd like to make it
> more official.
>
> I'd like to see changes start occurring in a branch if they are going
> to be anywhere from moderate to substantial. This gives you a chance
> to have the change reviewed, to play with the changes in a public way
> without affecting the users who seem to use trunk for no other reason
> than to use trunk, and should make trunk retain stability.
>
> As a for instance, Colin has been talking about changing the Get Info
> window up, that would need to go into a branch. But say we had a
> localization change, that'd still land into trunk and any branches it
> applied to.
>
> Make sense?
>
> Chris
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com





More information about the devel mailing list