Changes between Version 48 and Version 49 of TracCronPlugin

Timestamp:

Jan 17, 2016, 4:31:57 PM (8 years ago)

Author:

figaro

Comment:

Cosmetic changes, tagged with pypi

TracCronPlugin

@@ -11 +11 @@
  * Bundled out-of-the-box task
  * Scheduler are plugin
- * Bundled out-of-the-box scheduler '''new''' ''cron syntax is supported''
+ * Bundled out-of-the-box scheduler; '''new''': cron syntax is supported
  * Listener mechanism to be notified of task execution 
- * Bundled out-of-the-box listener '''new''' ''admin panel for listener''
- * Task execution history '''new''' ''rss feed is available''
+ * Bundled out-of-the-box listener; '''new''': admin panel for listener
+ * Task execution history; '''new''': rss feed is available
 
 The plugin provides an administration panel to help with scheduling:
@@ -31 +31 @@
 
 Current stable release is '''0.3.1'''.
+
 You can use easy_install or pip to download and install the latest package into your Python environment:
 {{{#!sh
@@ -117 +118 @@
 
 The plugin can be entirely configured from either trac.ini or the administration panel.
-The section name of TracCronPlugin is traccron, here is a full sample:
+The section name of TracCronPlugin is `traccron`, here is a full sample:
 
 {{{#!ini
@@ -137 +138 @@
 === Global settings
 
-This control the object called ticker which is the thread that launches tasks. If False, no ticket (no thread) is created, so your Trac behaves like there is no cron installed. This is the global setting you can act on to enable or disable all tasks. Default value is '''True''':
+This controls the object called ticker, which is the thread that launches tasks. If False, no ticket (no thread) is created, so your Trac behaves like there is no cron installed. This is the global setting you can act on to enable or disable all tasks. Default value is '''True''':
 
 {{{#!ini
@@ -175 +176 @@
 }}}
 
-This scheduler triggers a task that needs to be executed once a month. Provide the day in month and the hour when the task will be launched. The day is the index of the day starting at 1. Accepts comma separated value. Default is no value:
+This scheduler triggers a task that needs to be executed once a month. Provide the day in month and the hour when the task will be launched. The day is the index of the day starting at 1. Accepts comma separated values. Default is no value:
 
 {{{#!ini
@@ -214 +215 @@
 
 This task reminds the reporter about orphaned tickets and the assigned user about sleeping tickets.
- * An orphaned ticket is a ticket with status New since more than a given amount of days. An email notification is sent to the reporter in such a case.
- * A sleeping ticket is a ticket assigned to an user, but the user either did not accept it or did not touch the ticket (add a comment for example) since more than a given amount of day. The assigned user is notified in such a case. 
+ * An orphaned ticket is a ticket with status New for more than a given amount of days. An email notification is sent to the reporter in such a case.
+ * A sleeping ticket is a ticket assigned to a user, but the user either did not accept it or did not touch the ticket (added a comment for example) for more than a given amount of days. The assigned user is notified in such a case. 
 
 The delay is an optional parameter associated with each schedule. Default value is '''3 days'''.
@@ -223 +224 @@
 '''Note''': Since 0.2dev_r9388
 
-This task scan still opened tickets in near milestone. Such a situation means that those tickets will probably not be part of the milestone. The task sends a mail to user defined with ''unreachable_milestone.recipient'' (default is '''empty''') for each milestone with the list of still opened tickets. You may want to set the value to the release manager user. Reporter and owner are notified too, but only for their tickets. The task looks for the nearest milestone until '''3 days ahead'''. You can change the value with parameter either by setting ''unreachable_milestone.<schedule>.arg'' or in admin panel.
+This task scans still opened tickets in near milestone. Such a situation means that those tickets will probably not be part of the milestone. The task sends a mail to user defined with ''unreachable_milestone.recipient'' (default is '''empty''') for each milestone with the list of still opened tickets. You may want to set the value to the release manager user. Reporter and owner are notified too, but only for their tickets. The task looks for the nearest milestone until '''3 days ahead'''. You can change the value with parameter either by setting ''unreachable_milestone.<schedule>.arg'' or in the admin panel.
 
 This is an example of the mail for release manager:
@@ -255 +256 @@
 '''Note''': since 0.2dev_r9390.
 
-Trac allows the administrator to postpone still opened ticket in a given milestone when he closes this milestone. But this is not mandatory. The auto postpone task will help to not forget opened tickets in closed milestone. The task look for such tickets and postpone them in the more recent still opened milestone. Milestone must have a due date.
+Trac allows the administrator to postpone still opened ticket in a given milestone when he closes this milestone. But this is not mandatory. The auto postpone task will help to not forget opened tickets in a closed milestone. The task looks for such tickets and postpones them in the more recent still opened milestone. Milestone must have a due date.
 
 === Ticket deadline task
@@ -261 +262 @@
 '''Note''': since 0.3.
 
-This task notifies to the ticket's reporter and owner when its ticket is near the deadline as a custom field. You can add a date field for ticket using [http://trac-hacks.org/wiki/DateFieldPlugin DateFieldPlugin]. Besides scheduler settings, there are the following options to configure when DateFieldPlugin is used:
+This task notifies to the ticket's reporter and owner when its ticket is near the deadline as a custom field. You can add a date field for ticket using the DateFieldPlugin. Besides scheduler settings, there are the following options to configure when the DateFieldPlugin is used:
 
  - days_before: notify days before the deadline
@@ -269 +270 @@
 [[Image(ticket-with-duedate.png)]]
 
-Here is a sample configuration for trac.ini:
+Here is a sample configuration for the `trac.ini` file:
 
 {{{#!ini