Hello,
2014-03-04 15:32 GMT+01:00 Jaroslav Reznik <jreznik@xxxxxxxxxx>:
(Everyone), please keep the explicit "Proposal owners"/"other developers"/"release engineering"/"policies and guidelines" split. Other contributors need to know what they are being asked to do by your Change.
2014-03-04 15:32 GMT+01:00 Jaroslav Reznik <jreznik@xxxxxxxxxx>:
= Proposed System Wide Change: cron to systemd time units =
https://fedoraproject.org/wiki/Changes/cron-to-systemd-time-units
== Scope ==
(Everyone), please keep the explicit "Proposal owners"/"other developers"/"release engineering"/"policies and guidelines" split. Other contributors need to know what they are being asked to do by your Change.
* Policies and guidelines:
** Adjust packaging guidelines to mention migration of cron jobs to timer
units for packages that already depend on systemd
Last time this was discussed in http://meetbot.fedoraproject.org/fedora-meeting/2013-02-06/fesco.2013-02-06-18.00.log.html , there were concerns about "confusion of users/admins", specifically referring to the disabling a .service / disabling a .socket duality. So we will need packaging guidelines not only for the migration, but for the timer units themselves.
(From the Change page:)
Administrators will have better time trigger in units compared to cron jobs like for example when administrator stops a service/daemon the timer unit will stop as well etc.
This would also seem to require detailed packaging guidelines for the timer units.
* Fix spec files in packages that are not applicable for migration [Fix Cron
Dependency Tracking Bug 2]
* Review and migrate if applicable cron jobs shipped in packages that already
depend on systemd [Timer Migration Tracking Bug 3]
How many packages (at least an of magnitude) are we talking about? Is it the 16+3 that are currently blocking the tracker bugs?
Mirek
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
