Archive for August, 2008

LazyCure 3.4 is released

Wednesday, August 20th, 2008

LazyCure 3.4 is released. Here is a list of changes comparing with 3.3 version:

New features:

  • Task Manager is resized automatically in order to show all tasks without scrolling.
  • Possibility to delete tasks in Task Manager.
  • Notification when computer is shutdown.
  • Auto-generated unique activities names, if nothing is specified.
  • Switch time logs at midnight.

Bug fixes:

  • ‘Now you’ combobox is not active after pressing ‘Done’.
  • Activity and Task columns width could not be changed.
  • Bottom part of Main form is cut when no Activity Details.
  • When edit start, end is changed, but duration should changed - I love this bug fix especially!

By the way, LazyCure 3.4 is the most mature software for time logging I ever seen ;).

You can get LazyCure 3.4 on LazyCure Free Download page.

LazyCure Development Stategy

Saturday, August 16th, 2008

Let me introduce LazyCure Development Stategy - the common principals used by LazyCure developers (at the moment only by me :)).

One development cycle consists from 5 steps:

  1. Bug. Assign a bug to yourself before introducing any code changes.
  2. Red. Write a failing automated unit test before you write any code, which reproduces the bug. If unit test could not be created, add test case to LazyCureTest\LazyCure_TestCases.xls.
  3. Green. Write code in order to make unit test or test case passed.
  4. Refactor. Remove code duplication, verifying that all unit tests still passed. You can repeat 2-4 steps by introducing additional tests, related to the bug.
  5. Commit. Commit the code changes, specifying bug id and summary and any other details of maiden changes.

The following criteria is taken into the account when bug to fix is chosen:

  1. Priority.
  2. Severity.
  3. Creation time.

New LazyCure build could be created if there is at least one bug fixed and there are no bugs with priority 9 - Highest.

New minor LazyCure release could be created if at least one new feature is implemented and there are no bugs with priority 7 - High or higher.

New major LazyCure release could be created if at least one major feature is implemented and there are no bugs with priority 5 - High or higher.

The latest version of LazyCure Development Strategy could be found on http://lazycure.wiki.sourceforge.net/Development+Strategy page.