[Ilugc] software development practices
- From: lawgon@xxxxxxxxxxxxxxx (kenneth gonsalves)
- Date: Tue, 05 Jun 2012 16:01:19 +0530
On Tue, 2012-06-05 at 15:08 +0530, ??????? wrote:
this very rarely works out. My motto is - if you do not have a
client,
do not write software.
i am saying the practises adopted by Ubuntu, Fedora, Koha, Django,
KDE,
GNOME, OpenERP etc.,
How they put forth a timeline for every release, call for features to
be
added, bugs to be fixed, deadlines for translations, then alpha, beta
then the final release.
the only one I am familiar with is django - they fix a rough date for
release, but release when it is ready. They have rough list of features
for release, but those features get included only if someone gets them
ready. Same with translations. As for bugs, those described as release
blockers are fixed before release, if someone fixes others, they get
included in the release. In a purely voluntary community, that is all
that can be done. They do not have alpha, beta etc, they have release
candidate and release. I suspect that those projects where there are
companies backing them and paid developers, these things are more
systematic. Anyway if you have some experiences in these, please share.
(Koha has paid developers too)
--
regards
Kenneth Gonsalves
Other related posts: