LazyCure » Articles http://lazycure.com Learn more about yourself with LazyCure Thu, 24 Nov 2011 20:41:24 +0000 en hourly 1 http://wordpress.org/?v=3.3.2 LazyCure on Android http://lazycure.com/blog/lazycure-on-android http://lazycure.com/blog/lazycure-on-android#comments Thu, 24 Nov 2011 20:41:24 +0000 Mikhail Subach http://lazycure.com/?p=102 Do you need Android version of LazyCure? Please, answer in comments.

]]> http://lazycure.com/blog/lazycure-on-android/feed 20 How to contribute to LazyCure development http://lazycure.com/blog/lazycure-contribution http://lazycure.com/blog/lazycure-contribution#comments Sun, 21 Nov 2010 22:25:57 +0000 Mikhail Subach http://lazycure.com/?p=76 Continue reading →]]> If you would like to contribute to LazyCure development – it is easy! Here is the first and the single step:

Write me in Skype about your desire.

You can find by id ‘Scorpibear;. After that we discuss the details and your level of participation.

What is desired: C# .NET 4.0 + NUnit knowledge and Test-Driven Development skills.

Now I’m working on LazyCure 4.0 release, which could be localized to other languages. I am sure that Russian will be among them – and if you would like to see LazyCure in other languages – skype me. Or at least leave a comment here. I will be open with you – I know only Russian, English and Belorussian. So if you would like to see LazyCure in French, Ukrainian or Japanese – I need your help!;)

]]> http://lazycure.com/blog/lazycure-contribution/feed 0 LazyCure Development Stategy http://lazycure.com/blog/lazycure-development-stategy http://lazycure.com/blog/lazycure-development-stategy#comments Sat, 16 Aug 2008 09:58:28 +0000 Mikhail Subach http://lazycure.com/?p=20 Continue reading →]]> 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.

]]> http://lazycure.com/blog/lazycure-development-stategy/feed 0