id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
2	Release current version	DenisG	DenisG	My thoughts are:\r\n  * Provide a tarball of source code, ''also containing AprSharp source ?'' and MD prjx\r\n  * Provide a compiled assembly signed and strongly named for both ''AprSharp?'' and SubversionSharp\r\n\r\n Later:\r\n  * Add a better build solution than MD prjx, probably a working make file generated per MD may do it well\r\n	defect	assigned	normal	SubversionSharp 1.0	SubversionSharp	HEAD	normal		tarball dll assembly