Quick processes of development guarantee the possibility of growing articles and programs with the help of many participants. They have this way the opportunity to watch and/or test improvements or mistakes in non definitive versions, then solve them directly or by notifying other active members of the community.
Comment Agree with the wiki part, also that software should be released early to minimize not detecting important problems (verification vs. validation). One problem with too many releases can be: losing trust, because customers thinking why do they do this often, so buggy? Of course it can show an active development, but well... In the end it depends how one communicates this to the outside (e.g. software development process being used, marketing, ...) ----Erkan Yilmaz uses the Wikiversity:Chat 18:06, 19 January 2011 (UTC)
Support Alpha, Beta and other software release life cycle indicators could be understand equivalent to stages of articles ("to be expanded", "needs citation", etc) --Esenabre 15:15, 13 September 2010 (UTC)
Comment Agree with the wiki part, also that software should be released early to minimize not detecting important problems (verification vs. validation). One problem with too many releases can be: losing trust, because customers thinking why do they do this often, so buggy? Of course it can show an active development, but well... In the end it depends how one communicates this to the outside (e.g. software development process being used, marketing, ...) ----Erkan Yilmaz uses the Wikiversity:Chat 18:06, 19 January 2011 (UTC)
I disagree because