Whoops. This was meant to go to list, not just Andy.
-- Forwarded message --
From: Will Coleda <[EMAIL PROTECTED]>
Date: Jan 9, 2008 11:00 PM
Subject: Documentation Status: Was Re: Build status wiki page
To: Andy Dougherty <[EMAIL PROTECTED]>
On Jan 8, 2008 10
On Jan 8, 2008 4:32 PM, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> Speaking more broadly, I find parrot's development very scattered.
> It's hard to find stuff. Was it on a mailing list? on a web page?
> Which web page? launchpad? some blog site? perlfoundation.org?
> parrotcode.org? One of
On Sat, 5 Jan 2008, Andy Lester wrote:
> > Can you mention what platform tests were failing on? t/shootout isn't
> > failing anymore on any platform I have access to. It's very slow, but not
> > failing.
>
> No, I didn't mean that I would maintain it. I just started a place for people
> to keep
Can you mention what platform tests were failing on? t/shootout
isn't failing anymore on any platform I have access to. It's very
slow, but not failing.
No, I didn't mean that I would maintain it. I just started a place
for people to keep notes on, just to get inertia going.
Another rea
Andy Lester wrote:
I've started a wiki page for problems with builds/tests that are known
to be problems.
http://www.perlfoundation.org/parrot/index.cgi?build_status
This way we have a canonical place to look, rather than wondering "Hmm,
did this t/stm/*.t file pass before, or did I break it?
I've started a wiki page for problems with builds/tests that are known
to be problems.
http://www.perlfoundation.org/parrot/index.cgi?build_status
This way we have a canonical place to look, rather than wondering
"Hmm, did this t/stm/*.t file pass before, or did I break it?"
There's also a
