We don't branch anymore (our own study, as well as other's, showed that branching is a waste of time)
What other benefits does Mylyn have? I notice it has ties to subversive in Eclipse, but I've not installed it (I do use Subversive though)
Moderator: General Moderators
Can you elaborate or link? I can think of two scenarios right off the bat:Jenk wrote:We don't branch anymore (our own study, as well as other's, showed that branching is a waste of time)
Yeah but when an Engineer is working on the '10 model of the new car, he would not expect his boss to come and take the designs and ship them with '09 model. Also I think total rejection of branching would not work because bugs in previously released software do happen and do need to be fixed. Do you have any of those "studies" you mentioned though, or is this just your opinion (no offense)Jenk wrote:
Prototyping is also a development fallacy. There is no such thing as a prototype, only lazy development (i.e. not bothering to employ tests at the start) no body "throws away" what they first work on, so why not have it in a test harness from day one? You've then got tests to prove it (the app) won't break. We don't make models (e.g. motoring industry) as proof of concept, we don't do wind tunnel testing with 1:10 frames, etc. We produce software, and refactor it until it fits requirements.
Well, ideally... but lets say it was more than 2 hours of work. Do the changes get committed in progress?Jenk wrote:That's a poor example, because it wouldn't be just one field.. it would be the entire form, as a collection of input values.
So you just completely revert all work in progress, if there was a bug in a release from a month ago? What if you had 100 man hours in so far on the trunk. Do you think it would take more than 100 man hours to go back to a release branch, make the fix there and then merge it into the trunk? (rather then throw out the 100 man hours put in so far?)Jenk wrote:If there is an emergency, the sprint is terminated/aborted and we fix the emergency, then plan the next sprint (which will continue with the stories left out from the terminated/aborted sprint) this emergency work also includes time to remove/rollback unfinished features.
So the disadvantage of this approach would be that the trunk is too volatile to be deployed at any given time? (versus only merging stuff into the trunk once it is approved by QA and all stake holders)?If the boss or client walks in and demands a rollout/deployment and we aren't ready for one, we'll tell him/her so. The rollout plan will also include time to rollback.