On Mon, Aug 04, 2014 at 10:41:06PM +0100, Adam Dinwoodie wrote: > Just to update folk: I've bumped to v2.0.4, and everything's working a > lot more nicely. I've managed CVS imports using both 32-bit and 64-bit, > and I'm in the process of ironing out a few kinks in the test suites > before I'm ready to release. > > This definitely feels like the home stretch for getting something ready > to upload and distribute.
I think everything's good to go! CVS imports are working fine, I've used the build myself briefly (and a previous almost-identical build for a while), and the test suites are almost all passing*. I'm not sure what the process is for adopting somebody else's package; the "Submitting a new package" instructions don't seem to apply since it's not a new package, but I don't yet have upload rights to just go ahead and do it. The packages and setup.hint files are all ready to use and/or upload from http://tastycake.net/~adam/cygwin/. Before I can go ahead and release, I think I need to be added to cygwin-pkg-maint so I can send in an SSH key, and I possibly need a GTG from another maintainer. Adam * I've run all the tests I reasonably can and ironed out all the failures and unexpected skips except for a binary grep test that inexplicably passes, a CVS test that fails on 32-bit due to what looks like a bug in the cvs executable, and some rare 64-bit hangs when interacting with remotes that are sad but I don't believe should block the release.