On Wed, 21 Feb 2001 11:40:28 +0100, Richard Foley <[EMAIL PROTECTED]> wrote:
> Richard Soderberg wrote:
> >
> > On Wed, 21 Feb 2001, Richard Foley wrote:
> >
> > > a mail to [EMAIL PROTECTED] with the following (nearly inherent)
> > > hints:
> >
> > > category=dailybuild
> > > status=open|closed
> > > severity=fatal|high
> >
> > ack=yes|no
> >
> > Builds that have no test failures could be ok reports, too.
> > Builds that don't successfully compile get a severity=fatal.
> >
> > Very nice.
>
> Is 'dailybuild' appropriate, or should that read something else?
>
> I guess it would be sensible if it was something along the lines of the
> mailing list address name (smokers|testpilots|...) for consistency.
Should we report "Configure failures" as
[ ] Not at all
[ ] Success
[ ] Failure
[ ] Other
Here I mean that Configure is unable to proceed with the given configuration,
e.g. 'Configure -Dusethreads' on a system that does /not/ support threads or
'Configure -Duse64bitall' on an OS that does not support 64 bit operations.
--
H.Merijn Brand Amsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.005.03, 5.6.0, 5.6.1, 5.7.1 & 623 on HP-UX 10.20 & 11.00, AIX 4.2
AIX 4.3, WinNT 4, Win2K pro & WinCE 2.11 often with Tk800.022 &/| DBD-Unify
ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
