[local-time-devel] Local-time tests
Attila Lendvai
attila.lendvai at gmail.com
Sun Nov 18 20:52:20 UTC 2007
> I'm a little irritated that the local-time tests have gotten completely
> out of sync with the source. I only blame myself, since I haven't
> really been keeping up with the library at all for the past year.
i should have also run the testsuite more often... unfortunately in a
weak moment of mine i've started to port the testsuite to use stefil,
but gave up for various reasons, one of which is that stefil is our
lib and... so the suite was in a nonfunctional state for me lately.
but i've reverted the changes and will make sure to run the suite more
often.
> In the interests of sanity, however, I'd like to propose the following
> process:
>
> - All patches should be posted to local-time-devel for review and
> discussion
i'm using darcsweb and its rss feed to keep updated on what's
happening in the repos i'm depending on:
http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=local-time-local-time;a=summary
when your reader shows a patch (i use google.com/reader) you can
quickly get a diff, too. i'll push my patches to my public branch and
drop a mail to the list so you can review it and pull it if you agree
with it.
> - Patches which modify code should also include at least one test of the
> patch itself. The tests should fail before application of the patch,
> and succeed after the patch is applied.
>
> - No tests should fail after the patch is applied.
>
> Comments?
sounds good! theoretically i'm already following most of these -
except when practicality steps on my toes... :)
happy hacking,
--
attila
More information about the local-time-devel
mailing list