[scribus-dev] Branching/Forking Strategy
cbradney at scribus.info
Sat Mar 5 19:14:58 UTC 2016
> On 05 Mar 2016, at 19:03, John L. Poole <jlpoole56 at gmail.com> wrote:
> 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 libraries.
> Were this project in GitHub, I'd just create my on branch or fork.
> Does anyone have a suggested approach for my needs above?
Maybe you should suggest the changes be included and submit them via a bug on bugs.scribus.net?
More information about the scribus-dev