Peter Lemenkov recently suggested moving to git, and I thought that was
a good idea: I've been using git-svn to work with SIPp for a while and
find it a much better workflow. So I've created a git repository on
Sourceforge, which will now be the main code management for SIPp
(leaving the old SVN repository as a read-only archive):
I've merged in Peter's refactoring work, and also checked in an
improvement to time formatting that I previously discussed on the list.
I'll move the docs source over to git soon and update the link on the
homepage, and then see whether I can easily move the IMS Bench branch
to git as well.
There's also a "more_refactoring" branch where I've begun to move a few
more functions into more sensible places: this doesn't yet compile, but
I'm publishing it in case anyone wants to pick it up and work on it. I'm
hoping that this easy publishing of "work-in-progress" branches will be
an advantage of git.
Relatedly, I've been looking into setting up a build server, to compile
SIPp (with various options) and run unit tests after each checkin, and
make the results public. I've tried the CloudBees service, but it seems
to lack the PCAP headers required to build SIPp with PCAP support, which
is probably too limiting. I'm currently looking at inexpensive,
low-powered VPSes to give a bit more flexibility.
As always, comments (whether on the code or the project infrastructure)
are welcome and encouraged.