Hi Trans,
Sorry I've been out of the loop for a bit. I've been working on some other projects.I just emailed Charlie about working with him to get a new release out. How do we want to handle this? Should we tag the current version and allow the patches on trunk? Or create a branch and apply the patches there first?
Yeah, I was bad, and didn't tag the release in SVN. I can go back and do that, it would be a good idea.
There is going to have to be a 0.6.1 release fairly soon. The extconf.rb file in 0.6.0 doesn't work for Linux in some cases. The issue is the find_library call was incorrect (I didn't go back and look when that happened, but it was prior to 0.6.0 release). I've checked in a fix to SVN. Also Tom provided me another couple of patches.
Before we do that though I was wondering what others thought about of switching to Git?
Well, I know git is the new cool think in town. But I'm on Windows, and love TortoiseSvn, so I don't have any motivation to move to git (lousy windows support and no gui). I suppose it was easy to have some git/svn integration thing or some such I could be ok, but just seems like extra work to me for little benefit (its not like there are very many committers anyway).
Charlie
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
