When do you tag your software project?
Posted
by WilhelmTell of Purple-Magenta
on Stack Overflow
See other posts from Stack Overflow
or by WilhelmTell of Purple-Magenta
Published on 2010-04-21T22:51:34Z
Indexed on
2010/04/21
22:53 UTC
Read the original article
Hit count: 356
release
|project-management
I realize there are various kinds of software projects:
- commercial (for John Doe)
- industrial (for Mr. Montgomery Burns)
- successful open-source (with audience larger than, say, 10 people)
- personal projects (with audience size in the vicinity of 1).
each of which release a new version of their product on difference conditions. I'm particularly interested in the case of personal projects and open-source projects. When, or under what conditions, do you make a new release of any kind? Do you subscribe to a fixed recurring deadline such as every two weeks? Do you commit to a release of at least 10 minor fixes, or one major fix? Do you combine the two conditions such as at least one condition must hold, or both must hold?
I reckon this is a subjective question. I ask this question in light of searching for tricks to keep my projects alive and kicking. Sometimes my projects are active but look as if they aren't because I don't have the confidence to make a release or a tag of any sort for a long time -- in the order of months.
© Stack Overflow or respective owner