Sourceforge subversion problem

[afcouling]

There are multiple possible work flows that you can have, one such is the work flow used by the PHP project that migrated from subversion to git a while back. You can find details online, but basically they use https://github.com/php/php-src as their release repository, at the time of writing there are 4661 forks, each of which will issue pull requests to this repository, but they can of course pull code between them

Hi Tim,

I just checked out the PHP GitHub account.
It appears they have a branch for each version being developed, and merge the 'version' branches back into the master branch just before/after publishing releases.
I guess this results in the master branch always containing the current release.
Would you endorse this approach?

For the other Git novices like me, here's a useful article about Git branches and forks:
https://blog.scottlowe.org/2015/01/27/us...-workflow/

Andy.