Changes between Version 8 and Version 9 of ReScheduleScript

Timestamp:

Apr 13, 2022, 6:50:48 AM (20 months ago)

Author:

figaro

Comment:

Move example to functional description

ReScheduleScript

@@ -8 +8 @@
 
 It will probably work with Trac 0.10 and 0.9, all it depends on is the milestone table format.
-
-See the [#Example Example] section for more usage details.
 
 {{{
@@ -31 +29 @@
 }}}
 
+As an example:
+
+{{{#!sh
+python reschedule.py --dsn 'user=someuser host=localhost dbname=trac' \
+  --old 20071101 --start 20071203 --end 20090630 --dbtype postgres
+}}}
+
+would reschedule the milestones for a project that originally started 20071101 and ran until the due date of the last milestone to run instead between 20071203 and 20090630, which the same proportional allocation of time for each milestone.
+
+'''Note:''' without the {{{--commit}}} flag it just prints a table showing what the changes would be, without altering the database. Always test it without the {{{--commit}}} flag first.
+
 == Bugs/Feature Requests
 
@@ -51 +60 @@
 You can check out ReScheduleScript from [/svn/reschedulescript here] using Subversion, or [source:reschedulescript browse the source] with Trac.
 
-== Example
+== Installation
 
-{{{#!sh
-python reschedule.py --dsn 'user=someuser host=localhost dbname=trac' \
-  --old 20071101 --start 20071203 --end 20090630 --dbtype postgres
-}}}
-
-would reschedule the milestones for a project that originally started 20071101 and ran until the due date of the last milestone to run instead between 20071203 and 20090630, which the same proportional allocation of time for each milestone.
-
-'''Note:''' without the {{{--commit}}} flag it just prints a table showing what the changes would be, without altering the database. Always test it without the {{{--commit}}} flag first.
+General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page.
 
 == Recent Changes