Changes between Version 1 and Version 2 of ReScheduleScript
- Timestamp:
- Nov 27, 2007, 4:16:10 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReScheduleScript
v1 v2 4 4 5 5 This isn't a normal Trac Hack, but a small standalone python program that stretches or compresses milestones between new start and stop dates, keeping the time allocations for each the same, proportionally. 6 7 {{{ 8 Usage: reschedule.py [options] 9 10 Fit Trac milestone due dates into a new time range, preserving relative 11 spacing 12 13 Options: 14 -h, --help show this help message and exit 15 -D DBTYPE, --dbtype=DBTYPE 16 database type: sqlite (default), postgres, mysql 17 -d DSN, --dsn=DSN connect spec, eg. 'user=foo dbname=bar host=eg.com', 18 or a filename for sqlite systems 19 -s START, --start=START 20 new start date YYYYMMDD 21 -e END, --end=END new end date YYYYMMDD 22 -o OLD, --old=OLD old start date YYYYMMDD 23 -S SCHEMA, --schema=SCHEMA 24 name of schema containing milestone table 25 -c, --commit commit changes to table 26 }}} 6 27 7 28 == Bugs/Feature Requests == … … 23 44 == Example == 24 45 25 {{{python reschedule.py --dsn 'user=someuser host=localhost dbname=trac' --old 20071101 --start 20071203 --end 20090630}}} 46 {{{ 47 python reschedule.py --dsn 'user=someuser host=localhost dbname=trac' \ 48 --old 20071101 --start 20071203 --end 20090630 --dbtype postgres 49 }}} 26 50 27 51 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.