headers
Nigel Metheringham | 23 Jun 2004 11:59
Picon

Code quality measurements and automated checks

[This mailing list isn't dead - its just resting...]

There is an interesting bug report in the Red Hat bugzilla for exim:-
  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=125117

The pointer to this I was given said 
        Various print format warnings from someone with a real facist
        intel compiler. They all look harmless bugs but the ones I
        sampled are still there.

We obviously need to fix this specific problem, however there is also an
issue that new release procedures should aim to detect and eliminate
this sort of bug within development and before release.

So we need:-
      * Some form of lint or other facist checker
      * Common coding flaw checkers (ie the old gets stuff, and more
        recent)

and I am sure that others can add other requirements here.

Additionally it would be good if we had a good way of hooking the
distribution bug repositories in some way - picking up reported bugs.

Main reason for this message is to leave footprints in the archives - so
we have a note that it needs sorting some time...

	Nigel.
--

-- 
[ Nigel Metheringham           Nigel.Metheringham <at> InTechnology.co.uk ]
(Continue reading)

Permalink | Reply | 19 comments |
headers
Adam D. Barratt | 23 Jun 2004 12:59
Picon

Re: Code quality measurements and automated checks

[resent due to typoing my posting address the first time]

On Wednesday, June 23, 2004 10:59 AM, Nigel Metheringham
<Nigel.Metheringham <at> dev.intechnology.co.uk> wrote:

[...]
> Additionally it would be good if we had a good way of hooking the
> distribution bug repositories in some way - picking up reported bugs.

That's trivial to do for Debian - simply subscribe exim-dev to the PTS
(Package Tracking System) for the exim{,4} source packages.

See
http://www.uk.debian.org/doc/developers-reference/ch-resources.en.html#s-pts
-commands for further details.

Adam
Permalink | Reply | 0 comments |
headers
Adam D. Barratt | 23 Jun 2004 12:50
Picon

Re: Code quality measurements and automated checks

On Wednesday, June 23, 2004 10:59 AM, Nigel Metheringham
<Nigel.Metheringham <at> dev.intechnology.co.uk> wrote:

[...]
> Additionally it would be good if we had a good way of hooking the
> distribution bug repositories in some way - picking up reported bugs.

That's trivial to do for Debian - simply subscribe exim-dev to the PTS
(Package Tracking System) for the exim{,4} source packages.

See
http://www.uk.debian.org/doc/developers-reference/ch-resources.en.html#s-pts
-commands for further details.

Adam
Permalink | Reply | 2 comments |
headers
Colin Morey | 23 Jun 2004 15:25
Picon
Favicon

Exim Test suite

Does anyone know of a test suite that people could run against a newly
compiled version of exim. I'm specifically thinking of one targeted
towards package maintainers. 

Currently I just run a couple of basic manual tests,which is rather
labour intensive when testing on multiple architectures.  Ideally I'd
love some kind of "make test" that would say to me, "yes, everything
compiled, but the binary barfed on $test", that I could ask other people
(with different architectures to mine), to run and verify everything
works for them.

Cheers,

Colin

--

-- 
Colin Morey <peitolm <at> gentoo.org>
Permalink | Reply | 2 comments |
headers
Colin Morey | 23 Jun 2004 15:32
Picon
Favicon

Re: Code quality measurements and automated checks

On Wed, 2004-06-23 at 10:59 +0100, Nigel Metheringham wrote:

> Additionally it would be good if we had a good way of hooking the
> distribution bug repositories in some way - picking up reported bugs.
> 
Do we(Exim-Dev), really want a copy of all bugs filed against a build of
exim for a particular distribution, or do we want to ask the Maintainers
of the packages to forward all bugs onto the list?

Certainly we(Gentoo) can do the former if that's what's requested. 

> Main reason for this message is to leave footprints in the archives - so
> we have a note that it needs sorting some time...
> 
> 	Nigel.

Cheers,

Colin
--

-- 
Colin Morey <peitolm <at> gentoo.org>
Permalink | Reply | 10 comments |
headers
Nigel Metheringham | 23 Jun 2004 16:04
Picon

Bug reporting and monitoring [Was Re: Code quality measurements and automated checks]

[Subject changed - I should know better than to mix multiple issues into
a single message]

On Wed, 2004-06-23 at 14:32, Colin Morey wrote:
> Do we(Exim-Dev), really want a copy of all bugs filed against a build of
> exim for a particular distribution, or do we want to ask the Maintainers
> of the packages to forward all bugs onto the list?

I think the ideal is that all distributions have active and on-the-ball
developers who will deal with build issues themselves, and push
notifications of upstream bugs to the upstream source, ideally with well
tested and decently produced fixes in the form of patches which are
based on a known upstream release.

[takes off rose tinted spectacles]

I also realise that this won't happen.

It appears that in the case of gentoo & debian (as they are at present)
we will be able to depend on the exim component maintainers managing
things appropriately so that real bugs come up to
exim-dev/exim-bugs/bugzilla.

In the case of RH/Fedora as things are at the moment exim appears to be
a poor relation package - its not high on their priority list so things
could get left in their bugzilla to rot.  That means real bugs for us
could get lost.  This may be best fixed by a couple of interested
volunteers occasionally culling the bug list from RH bugzilla.  It would
also be an appropriate situation to have an exim.org address of some
form on the CC list for all exim bugs by default, but I am not sure if
(Continue reading)

Permalink | Reply | 9 comments |
headers
Colin Morey | 23 Jun 2004 16:27
Picon
Favicon

Re: Bug reporting and monitoring [Was Re: Code quality measurements and automated checks]

On Wed, 2004-06-23 at 15:04 +0100, Nigel Metheringham wrote:

> It appears that in the case of gentoo & debian (as they are at present)
> we will be able to depend on the exim component maintainers managing
> things appropriately so that real bugs come up to
> exim-dev/exim-bugs/bugzilla.
> 
Just for the record, what kind of format would the list want these
notifications in?
a short message to the url of the bug  with an overview? and/or a
straight CC of the list onto the Bug in question.

> In the case of RH/Fedora as things are at the moment exim appears to be
> a poor relation package - its not high on their priority list so things
> could get left in their bugzilla to rot.  That means real bugs for us
> could get lost.  This may be best fixed by a couple of interested
> volunteers occasionally culling the bug list from RH bugzilla.  It would
> also be an appropriate situation to have an exim.org address of some
> form on the CC list for all exim bugs by default, but I am not sure if
> their bugzilla can do that.
> 
I know that Gentoo's Bugzilla can be setup to CC all bugs assigned to a
given user to another address., and for ease of tracking all Exim bugs
on gentoo, I've setup exim-bugs <at> g.o 

> But there are other distros... most of whom don't ship exim so I guess
> that makes it easier :-)
> 
do We have a list of distros that ship exim, either as part of the base,
or part of a "ports" tree, (eg. OpenBsd/FreeBSD)
(Continue reading)

Permalink | Reply | 8 comments |
headers
Andreas Metzler | 23 Jun 2004 17:06

Re: Code quality measurements and automated checks

On 2004-06-23 "Adam D. Barratt" <exim-dev <at> adam-barratt.org.uk> wrote:
> On Wednesday, June 23, 2004 10:59 AM, Nigel Metheringham
> <Nigel.Metheringham <at> dev.intechnology.co.uk> wrote:
> [...]
> > Additionally it would be good if we had a good way of hooking the
> > distribution bug repositories in some way - picking up reported bugs.

> That's trivial to do for Debian - simply subscribe exim-dev to the PTS
> (Package Tracking System) for the exim{,4} source packages.
[...]

I would not suggest it, though. About 92% of the bugs reported
against the Debian exim package are Debian-specific, i.e. depend on
the packaging and are not related to exim's sourcecode.
             cu andreas
Permalink | Reply | 1 comment |
headers
Adam D. Barratt | 23 Jun 2004 17:40
Picon

Re: Code quality measurements and automated checks

On Wednesday, June 23, 2004 4:06 PM, Andreas Metzler
<eximusers <at> downhill.at.eu.org> wrote:

> On 2004-06-23 "Adam D. Barratt" <exim-dev <at> adam-barratt.org.uk> wrote:
>> On Wednesday, June 23, 2004 10:59 AM, Nigel Metheringham
>> <Nigel.Metheringham <at> dev.intechnology.co.uk> wrote:
>> [...]
>>> Additionally it would be good if we had a good way of hooking the
>>> distribution bug repositories in some way - picking up reported
>>> bugs.
>
>> That's trivial to do for Debian - simply subscribe exim-dev to the
>> PTS (Package Tracking System) for the exim{,4} source packages.
> [...]
>
> I would not suggest it, though. About 92% of the bugs reported
> against the Debian exim package are Debian-specific, i.e. depend on
> the packaging and are not related to exim's sourcecode.

Fair point. (And the "I don't understand how things work", "I filed an
identical copy of this yesterday", etc., etc. bugs).

It did answer Nigel's initial desire though. :-)

Adam
Permalink | Reply | 0 comments |
headers
Yann Golanski | 24 Jun 2004 11:13
Favicon

Re: Exim Test suite

Quoth Colin Morey on Wed, Jun 23, 2004 at 14:25:34 +0100
> Does anyone know of a test suite that people could run against a newly
> compiled version of exim. I'm specifically thinking of one targeted
> towards package maintainers. 

I did make one ages ago when I was working at Planet but that was very
specific to Planet's configuration files.  Of course, I have access to
neither now.  

Still, it should not be too hard to code something like that... Long and
tedious but not hard.  

Phil, did you use to have one?

--

-- 
yann <at> kierun.org                  -=*=-                      www.kierun.org
    PGP:   009D 7287 C4A7 FD4F 1680  06E4 F751 7006 9DE2 6318
Permalink | Reply | 1 comment |

Gmane