Add the long awaited 'maintainer notification' system. This system, running from the cron
cleanup scripts, will look for maintainers that have queued entries that the maintainer can process. If the queued entries aren't processed for X days an email is sent. In X*2 days another email is sent. After X*3 days the maintainer is stripped of their maintainership as they aren't really maintaining the application anyway. The hope is that this system lets maintainers know that they have pending queued entries to process to reduce the pressure on the appdb admins to handled hundreds of queued entries.
This commit is contained in:
@@ -12,13 +12,15 @@ drop table if exists appMaintainers;
|
||||
* for both queued and unqueued maintainers
|
||||
*/
|
||||
create table appMaintainers (
|
||||
maintainerId int not null auto_increment,
|
||||
appId int,
|
||||
versionId int,
|
||||
userId int,
|
||||
maintainReason text,
|
||||
superMaintainer bool,
|
||||
submitTime datetime,
|
||||
queued enum('true','false','rejected') NOT NULL default 'false',
|
||||
maintainerId int not null auto_increment,
|
||||
appId int,
|
||||
versionId int,
|
||||
userId int,
|
||||
maintainReason text,
|
||||
superMaintainer bool,
|
||||
submitTime datetime,
|
||||
queued enum('true','false','rejected') NOT NULL default 'false',
|
||||
notificationLevel int not null default '0',
|
||||
notificationTime datetime,
|
||||
key(maintainerId)
|
||||
);
|
||||
|
||||
Reference in New Issue
Block a user