On Thu, Nov 06, 2008 at 12:48:42 -0700, zooko wrote: > 1. Temporarily revert the behavior of creating darcs-2-format > repositories by default, until after the next stable release.
Sorry, but I think I must step in with my first categorical "no" :-) This kind of behavioural ping-pong is harmful for everybody, developers and users alike, and we should avoid it when possible. In the short run, users that are resisting this upgrade could, as an alternative to upgrading to darcs 2.1, upgrade to darcs 2.0.2 instead whilst waiting for darcs 2 to be more widespread in their organisation. In any case, darcs 2 is here to stay, with people already opting to use the new hashed and darcs-2 format repositories. So while I appreciate the difficulty folks may have in rolling out darcs 2 in their organisations, upgrading, and expecting other users to upgrade is really the best move in the long run. > 2. Make the buildbot green. Once the buildbot turns green, then it > will automatically upload the Windows binary of darcs which passed all > unit tests to https://zooko.com/darcsbuildbot/uploads/ > zooko_allmydata_virtual2 , so that is the first element of: This is addressed in my previous message > 3. Automate the production of complete binary packages for many > platforms. Indeed, this would be a very worthy objective to aim towards (and as I understand it, we are very close to reaching this objective) In the short term, we desperately need a working binary for darcs 2.1.0 + 0 patches on Windows. I have a version on http://code.haskell.org/~kowey/tmp/darcs.exe but I believe it needs to be combined shipped with some OpenSSL dlls and one other from Microsoft. May I have a Windows volunteer to look into this? Many thanks, -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
