Small changes, release often or Big changes, release less?
Moderator: General Moderators
- Chris Corbyn
- Breakbeat Nuttzer
- Posts: 13098
- Joined: Wed Mar 24, 2004 7:57 am
- Location: Melbourne, Australia
Small changes, release often or Big changes, release less?
I personally like to keep pushing out new releases of code even if the changes I've made are small. I think it's healthy to have a code base which keeps improving, providing that every time you release a new version you don't require your users to modify anything.
It seems many people think this is silly though. What do you guys see as a good development cycle?
I make new releases around once a week although I have bursts where new releases will appear every couple of days. Obviously as the code matures more and more the releases will possibly become less frequent.
It seems many people think this is silly though. What do you guys see as a good development cycle?
I make new releases around once a week although I have bursts where new releases will appear every couple of days. Obviously as the code matures more and more the releases will possibly become less frequent.
- Ambush Commander
- DevNet Master
- Posts: 3698
- Joined: Mon Oct 25, 2004 9:29 pm
- Location: New Jersey, US
- Ambush Commander
- DevNet Master
- Posts: 3698
- Joined: Mon Oct 25, 2004 9:29 pm
- Location: New Jersey, US
Which I do as well on testing servers. I find it's easier to use WebDavFS to run the latest trunk code straight from the repository than to wait until the test pad would pick up the latest changes (never bothered to create appropriate post-commit hooks).If you're real crazy (like the MediaWiki developers), you'll run the code straight out of the repository with little to no lag time.
- RobertGonzalez
- Site Administrator
- Posts: 14293
- Joined: Tue Sep 09, 2003 6:04 pm
- Location: Fremont, CA, USA
Smaller updates, but not like everyday updates. If there are issues that need resolving in the code, then resolve the issues and post an update. If there are things that users/developers want to see in the code, develop those as time permits, then when the next update ocurrs, include it. I think too many updates kills the interest in an app ('Does the product keep changing because they haven't gotten it right, or what's the deal?').