Changes between Version 7 and Version 8 of ReScheduleScript
- Timestamp:
- Nov 23, 2015, 3:43:56 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReScheduleScript
v7 v8 33 33 == Bugs/Feature Requests 34 34 35 '''Note:''' the {{{--dbtype}}} flag is untested, I developed this for a postgresbased system.35 '''Note:''' the {{{--dbtype}}} flag is untested, I developed this for a PostgreSQL based system. 36 36 37 37 Existing bugs and feature requests for ReScheduleScript are … … 45 45 == Download 46 46 47 Download the zipped source from [ download:reschedulescript here].47 Download the zipped source from [export:reschedulescript here]. 48 48 49 49 == Source 50 50 51 You can check out ReScheduleScript from [ http://trac-hacks.org/svn/reschedulescript here] using Subversion, or [source:reschedulescript browse the source] with Trac.51 You can check out ReScheduleScript from [/svn/reschedulescript here] using Subversion, or [source:reschedulescript browse the source] with Trac. 52 52 53 53 == Example … … 60 60 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. 61 61 62 '''Note:''' without the {{{--commit}}} flag it just prints a table showing what the changes would be, without altering the database. 62 '''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. 63 63 64 64 == Recent Changes