Re: release scripts
Frans Englich <frans.englich <at> telia.com>
2004-02-01 17:28:42 GMT
On Sunday 01 February 2004 17:50, Benjamin Meyer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have noticed me and many others (on and off the list) doing tasks that
> could be done by scripts.
Fully agreed. I think it will save us a lot of trouble. We need a
regression/automating framework, and a place where such scripts are run
periodically.
There must be some unified way of adding/"registering" regtests("regression
tests"). In case the script can't fix the problem itself(it's an obvious
s/regexp/regexp/ ie.) the regtest will have to send it's output somewhere. A
script which runs over all kde modules(checking licenses for example) can't
just send it to one person(or what do you say, Coolo? :). Perhaps each
directory relevant for the regtest should contain a file where there's
contact information for that dir(and if it is recursive, etc.). Perhaps it
could be extracted from the apidocs. Whom to contact would could also depend
on the tpe of output(critical vs coding style ie.). When contact persons
can't be reached it must fallback to another contact(mailinglist,
maintainer).
I have absolutely no experience in this field, does there already exist such
software? Are there any plans for this already?
> It might be a good idea in kdesdk to create a
> directory where scripts can reside that check over cvs for problems. Some
> scripts that I can think of off the top of my head are:
>
> - -Check to make sure that icons that say they are size YxY really are that
(Continue reading)