Dirk wrote:
My plan is to create a branch tonight for 0.10, which will be the
basis of all future 0.10 releases, so that further work can continue
on the trunk. I'll also hopefully tag and release 0.10-beta, as well
as generate a release zipfile with vss2svn.exe and ssphys.exe.
I have closed two of them. #15 isn't assigned for any milestone.
If you created the branch, I will checkout the source and compile
ssphys again in order to have the correct "revision" information
displayed in the --version information. Just give me a small note,
when you finished creating the tag.
OK, I've created branches/release/0.10 for any further work on the 0.10
version. I've also tagged Beta 1 as tags/0.10.0-b1. I'll "officially"
release 0.10 Beta-1 once I create the zipfile.
I will plan on getting a 0.10 release candidate out soon; at this point
the only changes I'm planning on will be cosmetic (improving output,
scaling back some of the error messages). I also need to get the online
docs in better shape.
Dirk, please go ahead and post the ssphys.exe to the FTP area for the
time being, although I need to revisit that and either set up an https
webform or use scp... I don't mind so much using cleartext passwords
over http for Subversion and Trac, but for .exe's that people will be
downloading I need a better solution...
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
