What's your release process for your commercial application?
Posted
by dr. evil
on Stack Overflow
See other posts from Stack Overflow
or by dr. evil
Published on 2010-03-17T11:50:23Z
Indexed on
2010/04/06
15:43 UTC
Read the original article
Hit count: 311
If you are developing a commercial desktop application, what's your release process?
Sample process:
- Develop it: Patch bugs, add features, etc.
- Feature Freeze (do not fix, add anything unless it's absolutely required)
- Test it
- If everything is OK release it, if it's not fix it, test it, release it
I think the most crucial question is what's your approach to "feature freeze > test > release" cycle?
Or do you test it more frequently that you don't need such a cycle and your software is always ready for public release?
© Stack Overflow or respective owner