On Thursday 03 January 2013 20:14:23 William S Fulton wrote:

With the new year we have switched SWIG development to a new development model - Git on Github. The old Subversion history (including the even older CVS history) has been migrated and is now viewable in Github - https://github.com/swig/swig . If you have used SWIG we would really appreciate improvements you have made for incorporation into the mainline SWIG releases. So, feel free to use Github to fork and send your pull requests or patches.

Improvements to the documentation are also very welcome - the docs can be found at
https://github.com/swig/swig/tree/master/Doc/Manual .

Information for getting going is on the SWIG website:
http://www.swig.org/svn.html .

We have also turned on the new SourceForge Allura system which is much slicker than the old SourceForge for submitting bugs/patches -
https://sourceforge.net/projects/swig/ .

Happy new year!
William

A meta question...

 

I have cloned the master repository and have been playing on a private branch for my guile updates.

 

I don't think my work is ready yet to be merged into the main repo. But I'd like to publish what I have so far to gather feedback.

 

Since I have been working on a private branch so far, it was easy to rebase my branch to the latest master HEAD. But I read here and there that rebasing published branches is not really recommended.

 

So I wonder what swig's public branch policy is ?

 

I can push my branch to a cloned git repo, so others can look into it there or pull it into their own local repos. Can I still rebase it afterwards without causing too much frustration for other developers ?

 

Or should I start merging the master branch into my personal branch regularly from there on ?

 

How do other developers handle this ?

 

Geert