Since we'll be dealing with a more diverse repository set, I'd like to do the following things:
* Move the TODO to the wiki. I don't want to deal with merging this, if it changes, and it's mostly untouched anyways... Of course, keep a URL in the TODO so people can open the file and know where to look. * Split ChangeLog out to separate files for each version, possibly as ReleaseNotes-$VERSION instead and allow us to be more freeform in our entries. It'll be less likely to grow huge over the years, too Our ChangeLog is fairly small, so this isn't likely to be a problem with git, either. Humongous, frequently growing changelogs for projects (previously on cvs/svn) like gcc don't work well with the limited delta lengths that git uses. Technical changelogs don't make sense in git repos since "git log" is so readily available to developers. Additionally, a user-oriented NEWS / ReleaseNotes system would actually benefit users that get mpd from the tarball or vendor (our ChangeLog is actually closer to what I'd expect from a NEWS file). -- Eric Wong ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
