Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 627600 - cron-bugs: no reply to project status mail
Summary: cron-bugs: no reply to project status mail
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Cron Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-12 06:52 UTC by Michał Górny
Modified: 2019-09-23 16:13 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-08-12 06:52:39 UTC 
On 2017-07-18 a mail inquiring project status was sent to project alias. I do not have any reply registered for this project.

If you have not received the mail, please contact me. If I missed your reply, then I'm sorry, please just let me know. Otherwise, please look into replying to that mail. The reply is important to determine the project status and the steps to follow.
Comment 1 Anthony Basile gentoo-dev 2017-12-20 19:54:04 UTC 
(In reply to Michał Górny from comment #0)
> On 2017-07-18 a mail inquiring project status was sent to project alias. I
> do not have any reply registered for this project.
> 
> If you have not received the mail, please contact me. If I missed your
> reply, then I'm sorry, please just let me know. Otherwise, please look into
> replying to that mail. The reply is important to determine the project
> status and the steps to follow.

i'm giving cron-bugs some love.
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2019-03-27 13:07:49 UTC 
Do you think it makes sense to keep project dedicated to different cron implementations?  Maybe it'd be better to look for maintainers that would be interested in individual packages instead.
Comment 3 Larry the Git Cow gentoo-dev 2019-03-29 13:03:03 UTC 
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=03ad7a250f300994d519e9b08a33fdcd7090f033

commit 03ad7a250f300994d519e9b08a33fdcd7090f033
Author:     Michał Górny <mgorny@gentoo.org>
AuthorDate: 2019-03-29 13:02:08 +0000
Commit:     Michał Górny <mgorny@gentoo.org>
CommitDate: 2019-03-29 13:02:08 +0000

    */*: Remove cron-bugs@ from maintainers
    
    Bug: https://bugs.gentoo.org/627600
    Signed-off-by: Michał Górny <mgorny@gentoo.org>

 eclass/cron.eclass                  | 4 ++--
 sys-process/anacron/metadata.xml    | 5 +----
 sys-process/at/metadata.xml         | 4 ----
 sys-process/bcron/metadata.xml      | 5 +----
 sys-process/cronbase/metadata.xml   | 6 +-----
 sys-process/cronie/metadata.xml     | 6 +-----
 sys-process/dcron/metadata.xml      | 4 +---
 sys-process/fcron/metadata.xml      | 4 ----
 sys-process/vixie-cron/metadata.xml | 5 +----
 virtual/cron/metadata.xml           | 6 +-----
 10 files changed, 9 insertions(+), 40 deletions(-)
Comment 4 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2019-03-29 13:10:32 UTC 
Ok, I've updated metadata.xml, sent 'up for grabs' and reassigned bugs (including some old bugs that haven't been reassigned when maintainers changed).  I've assigned some generic bugs to blueness (as maintainer of cronbase), and I've kept cron-bugs@ CC-ed everywhere for smoother transition.

Please let me know if I should keep the CRON project and alias for some extra time, or disband them already.
Comment 5 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2019-09-23 16:13:58 UTC 
Wiki page cleaned, I'll kill bugzilla alias now.