> SourceForge projects aren't required to use CVS, and on single-man teams
> like JPluck currently (and one of the projects I'm doing), CVS doesn't
> make a whole lot of sense.
A few flaws in your assertion:
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?
2.) How can I find out what changed between the two versions,
without downloading both (except I can't, one isn't available)
and diffing every single file as a whole or individually
recursively?
3.) Enabling CVS is a single-button toggle for you in the SourcForge
interface, and doesn't in any way increase your management
resources of the project, as a lone-developer of it.
4.) You're not encouraging other people to help developing on JPluck
if they can't see the source directly and check it out from CVS.
5.) CVS is not just a way "to download the source", it's a way to
track the development and maturity of the source, through
ChangeLogs, diffs, and metadata.
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?
Sure, I can diff two versions (assuming you released source for two
incremental versions, of course), but that doesn't tell me WHY you changed
one piece of code. Where are the actual commit messages related to each
change? I don't see a ChangeLog in your tarball of binary+source downloads.
> The projects are required to release the source, but there's no
> requirement that they do it via CVS.
I'm well aware of what is required, but thanks for the reminder.
CVS enhances the way people can use the code, and enables others to
more-closely follow the development, should they care to see if their bug
was fixed, or if your change to an API breaks their code that relies on that
API, and so on.
In any case, it's your project, and you can do what you want with
it, just realize that you're not the only one of probably dozens of people
who is using that codebase.
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.
Having CVS available would prevent this problem, and remove your
need to create tarballs of the source for download, since you can just tag
the source in CVS, and point people there.
d.
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
