NAME

base_aegi_notify.pl - handle Aegis notifications.

COPYRIGHT

Copyright (C) 2001, 2002 Mark Veltzer; All rights reserved.

LICENSE

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111, USA.

DETAILS

        MANIFEST: base_aegi_notify.pl
        PROJECT: meta
        VERSION: 0.28

SYNOPSIS

        base_aegi_notify.pl

DESCRIPTION

This script will be activated by Aegis each time an event worthy of notification occurs (integration or other stuff...).

OPTIONS

help (type: bool, default: 0)

display help message

pod (type: bool, default: 0)

display pod options snipplet

man (type: bool, default: 0)

display manual page

quit (type: bool, default: 0)

quit without doing anything

gtk (type: bool, default: 0)

run a gtk ui to get the parameters

license (type: bool, default: 0)

show license and exit

copyright (type: bool, default: 0)

show copyright and exit

description (type: bool, default: 0)

show description and exit

history (type: bool, default: 0)

show history and exit

verbose (type: bool, default: 0)

noisy or quiet ?

demo (type: bool, default: 0)

do it or just play pretend ?

minimum of [1] free arguments required no maximum limit on number of free arguments placed

BUGS

None.

AUTHOR

        Name: Mark Veltzer
        Email: mailto:veltzer@cpan.org
        WWW: http://www.veltzer.org
        CPAN id: VELTZER

HISTORY

        0.00 MV initial code brought in
        0.01 MV make quality checks on perl code
        0.02 MV more perl checks
        0.03 MV make Meta::Utils::Opts object oriented
        0.04 MV more harsh checks on perl code
        0.05 MV fix todo items look in pod documentation
        0.06 MV more on tests/more checks to perl
        0.07 MV silense all tests
        0.08 MV more perl quality
        0.09 MV perl code quality
        0.10 MV more perl quality
        0.11 MV more perl quality
        0.12 MV more perl quality
        0.13 MV revision change
        0.14 MV languages.pl test online
        0.15 MV perl packaging
        0.16 MV more Perl packaging
        0.17 MV license issues
        0.18 MV md5 project
        0.19 MV database
        0.20 MV perl module versions in files
        0.21 MV thumbnail user interface
        0.22 MV more thumbnail issues
        0.23 MV website construction
        0.24 MV improve the movie db xml
        0.25 MV web site automation
        0.26 MV SEE ALSO section fix
        0.27 MV move tests to modules
        0.28 MV md5 issues

SEE ALSO

Meta::Baseline::Aegis(3), Meta::Baseline::Test(3), Meta::Info::MailMessage(3), Meta::Utils::Opts::Opts(3), Meta::Utils::Output(3), Meta::Utils::System(3), strict(3)

TODO

-do the actual notifications and use some perl email module to do that.

-move all the code here to some lower level (pm modules).

-once Utils::Opts supports enum types move the free argument to an enum type...:) (that way we wouldnt have to handle the error messages here...)

-today we follow the following algorithm for notifications: gather all developers, reviewers, integrators and administrators and send them the mail about the condition changing. Could we not have a much more sophisticated scheme in the baseline whereby people will only get the mail about stuff they are interested in and in any case there will be a file in the baseline (in /data) with general policies (like develop_end going to reviewers etc...?