* **Update:** Removed ``TimeLog._expand_task_schedule_timing()`` method which was automatically adjusting the ``schedule_timing`` and ``schedule_unit`` of a Task to total duration of the TimeLogs of that particular task, thus increasing the schedule info with the entered time logs.
But it was setting the ``schedule_timing`` to 0 in some certain cases and it was unnecessary because the main purpose of this method was to prevent TaskJuggler to raise any errors related to the inconsistencies between the schedule values and the duration of TimeLogs and TaskJuggler has never given a real error about that situation.
0.2.7.5
=======
* **Fix:** Fixed Task parent/child relationship, previously setting the parent of a task to None was cascading a delete operation due to the "all, delete-orphan" setting of the Task parent/child relationship, this is updated to be "all, delete" and it is now safe to set the parent to None without causing the task to be deleted.
0.2.7.4
=======
* **Fix:** Fixed the following columns column type from String to Text:
* **Update:** It is now possible to create TimeLog instances for a Task with PREV status.
0.2.7.3
=======
* **Fix:** Fixed ``Task.update_status_with_dependent_statuses()`` method for a Task where there is no dependency but the status is DREV. Now calling ``Task.update_status_with_dependent_statuses()`` will set the status to RTS if there is no ``TimeLog`` for that task and will set the status to WIP if the task has time logs.
0.2.7.2
=======
* **Update:** ``TaskJugglerScheduler`` is now 466x faster when dumping all the data to TJP file. So with this new update it is taking only 1.5 seconds to dump ~20k tasks to a valid TJP file where it was around ~10 minutes in previous implementation. The speed enhancements is available only to PostgreSQL dialect for now.
0.2.7.1
=======
* **Fix:** Fixed TimeLog output in one line per task in ``Task.to_tjp()``.
* **New:** Added ``TaskJugglerScheduler`` now accepts a new argument called ``compute_resources`` which when set to True will also consider `Task.alternative_resources` attribute and will fill ``Task.computed_resources`` attribute for each Task. With ``TaskJugglerScheduler`` when the total number of Task is around 15k it will take around 7 minutes to generate this data, so by default it is set to False.