> Btw. I'm asking me if it would be better to have a smaller scope for each > release, but release more often. > With a rather small team of developers, I think this would have several > advantage > - focused on a fewer numbers tickets
Believe me, this will not happen :-) A lot of people will tell you their ticket is very important and needs to be in the upcoming release... > - a higher quality could be achived this way Not sure, you can screw up a small release too. I think that good tests will help a lot. Don't do structural changes (prototype->jquery, rails2->3, database changes, large refactoring) if not necessary. Reviewing each other's patches helps. Furthermore, develop new stuff on branches and keep master stable seems to work. Consider _why_ stuff is failing (missing test, not thought about the failing scenario, unfinished implementation) > - a individual release is managable, so easier to plan Planning releases where developers work in their spare time will not work :-) Diapers and stuff will get a higher priority :-) > - more feedback on new features > - more motivation to implement a ticket for the current release, as result will > be published sooner. This is a big advantage, although I do think people contributing a patch are able to run master for themselves... Reinier _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
