[scribus-dev] Branching/Forking Strategy

John L. Poole jlpoole56 at gmail.com
Sat Mar 5 18:03:09 UTC 2016

I have enough tweaks that I'd like to check my changes and additions 
into some sort of source control.  Given how large the Subversion tree 
is for this project, I'm wondering what is the best strategy to be able 
to source control my own changes/additions locally?  I could make a copy 
to my own Subversion repository, but then merging changes from your 
trunk into my copy seems complicated.  I'd like to keep track of weekly 
updates and see if I can compile windows builds on a weekly basis.  This 
would occur after I finish my Perl scripts for juggling the supporting 

Were this project in GitHub, I'd just create my on branch or fork.

Does anyone have a suggested approach for my needs above?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus-dev/attachments/20160305/2e39e862/attachment.html>

More information about the scribus-dev mailing list