On Wed, May 21, 2008 at 5:21 AM, Eric Kow <[EMAIL PROTECTED]> wrote: > It may be time to start thinking about the next version of darcs (say, > for early 2009). ... > (1) critical/urgent bugs - darcs 2.0.0 seems much more robust than > darcs 1, but we still do have at least one case where it blows up > (issue857) and another where doing funny things can have surprising > results (issue687).
I've been meaning, one of these days, to put out a darcs 2.0.1 release. There are a few embarrassing bugs in 2.0.0 that I'd like to see fixed. Right now, I believe issue857 is the only remaining stopper. Of course, it isn't a regression from 2.0.0, so there's no reason why it *need* block a release, but I'd rather get it fixed first (and just submitted a grant proposal yesterday, so maybe now I'll have time and energy?). A 2.0.1 release should really consist of me stopping allowing non-bugfixes for a while, then tagging, updating configure.ac, and making tarballs. So how about no new features or performance patches from now until 2.0.1 is released? (I feel bad that I let in the Lcs rewrite, which included a but, just recently...) David _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
