> 1.) You released JPluck 2.0-pre13 in a Windows-only executable, sans > source. Where is the source for that? I see 2.0-pre12, but where > s pre13?
Just to be clear: you are responding to Tony, not to me. Anyway, source code is included in the distribution. It's just that you need to run the Windows setup to get to it. ;-) There is no pre13 distribution for other platforms as all changes since pre12 are Windows-specific. I've added a list of the distribution contents to the JPluck 2 page [1]. > Your assertion that "CVS doesn't make a whole lot of sense" fails to > include the countless thousands of users and developers who wish to see the > metadata, diffs, changes, ChangeLog, and so on that is only contained within > cvs itself. With a tarball of source, how can I see what changed and why? I can't speak for Tony, but I don't want to go through the hassle of maintaining a CVS repository for a one-man project just so that others can track project changes. To be honest: some the JPluck code is quite embarrassing and CVS will make that all the more visible, so I'd rather not. There are many widely-used OSS projects that don't maintain a CVS repository. (Saxon is one example that springs to mind.) > I would request, however, that you release the source which matches > the binaries you distribute. You're still not in lockstep with that yet on > at least 3 other previous releases (0.9.1.1, 0.9.1, and 0.9.1), as well as > the most-recent 2.0-pre13. All JPluck 0.x binary distributions have a corresponding "developer" source distribution. I may have mismatched package visibility in the file release list, though. At any rate, all uploaded packages are still available [2], SourceForge won't let you delete them. Regards -Laurens [1] http://jpluck.sourceforge.net/jpluck2/index.html [2] http://prdownloads.sourceforge.net/jpluck/ _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
