Michael Olson <[email protected]> wrote: >> If no one else has something to say about that, we can work on this >> scheme: >> - see the diffs between the old 3.0 and HEAD, and extract patches that >> are bugfixes, to make a 3.1 release >> - update the version number in HEAD to be 4.0dev >> - RELEASE!
> I'd recommend against making some kind of "patch soup" approach for > 3.1, where select patches are taken out and applied against 3.0. The > reason for this is that it will likely not receive much testing. > Instead, why not just finish the remaining tasks for the next release > (or push them out to release+1) and release that instead? +1. 3.0 is now more than three years (!) old, and if someone has lived with its bugs (if there are any) for that long, he probably won't care about 3.1 anyhow. "It's dead, Jim." I just want to leave room for the /possibility/ for bug fixes/maintenance work in the version scheme so that we don't have to make up some ad-hoc rule if we ever encounter the necessity to release one. Tim _______________________________________________ Emms-patches mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emms-patches
