On Mon, Jan 12, 2009 at 18:04, mrts wrote:
> As of now, I'll stop pursuing this further, but when I come back to
> this,
> would the approach outlined in http://dpaste.com/108140/ be
> acceptable?
>
> I.e. if
> 1) not specified explicitly (by the --multiprocessing option to test)
> 2) there's onl
On Jan 12, 3:45 pm, "Jacob Kaplan-Moss"
wrote:
> On Mon, Jan 12, 2009 at 6:53 AM, mrts wrote:
> > What if we try to be nice to ourselves and get #8138 and something in
> > the lines ofhttp://oebfare.com/blog/2008/mar/25/faster-django-test-suite/
> > into trunk ASAP
>
> #8138 is nearly done; th
On Mon, Jan 12, 2009 at 5:53 AM, mrts wrote:
> What if we try to be nice to ourselves and get #8138 and something in
> the lines of http://oebfare.com/blog/2008/mar/25/faster-django-test-suite/
> into trunk ASAP, especially now that the dynamic workflow is really
> gaining ground (both aggregate
On Mon, Jan 12, 2009 at 7:44 AM, Karen Tracey wrote:
> (There was a mini-sprint on Saturday? I missed the memo -- where are these
> things being announced or was this just impromptu?)
It was really just a handful of us in Lawrence getting together for
the afternoon; those who were in #django-de
On Mon, Jan 12, 2009 at 6:53 AM, mrts wrote:
> What if we try to be nice to ourselves and get #8138 and something in
> the lines of http://oebfare.com/blog/2008/mar/25/faster-django-test-suite/
> into trunk ASAP
#8138 is nearly done; there are still a couple of tricky issues to
work out first. T
On Mon, Jan 12, 2009 at 8:25 AM, James Bennett wrote:
>
> On Mon, Jan 12, 2009 at 6:53 AM, mrts wrote:
> > What if we try to be nice to ourselves and get #8138 and something in
> > the lines of
> http://oebfare.com/blog/2008/mar/25/faster-django-test-suite/
> > into trunk ASAP
>
> What if we pay
On Mon, Jan 12, 2009 at 6:53 AM, mrts wrote:
> What if we try to be nice to ourselves and get #8138 and something in
> the lines of http://oebfare.com/blog/2008/mar/25/faster-django-test-suite/
> into trunk ASAP
What if we pay attention to the work that's been done on that
recently, including du
A proper "agile" workflow for distributed collaboration on a largeish
chunk of functionality should be as follows:
Feature developer:
* implement tests for the features to be added
* commit locally
* implement the features
* commit locally
* run the test suite iteratively, fixing whatever the tes
