On Aug 13, 2012, at 2:52 PM, Alex Harui wrote: > > >> >> Really what is the worst that can happen if someone plays in trunk and makes >> a >> mistake? >> >> Regards, >> Dave >> > For me, I don't like the psychology of reverting someone's changes, or even > my own. It feels like going backward. If the only public copy of some work > goes in trunk and then gets removed from the release branch, there is always > a chance that you'll mess up the re-integration. Yes, it is always in the > history to be fished out, but I'd rather avoid that.
I am thinking about the psychology of working on a change and getting it all working in "unstable" and then waiting to see if the RM or PPMC or who exactly decides it is good enough to be in "stable" trunk. If I'm a committer then I should be trusted to not screw it up in the first place. If the project thinks it is near release then the group ought to work in not making unstable changes to trunk. We are all grown ups here aren't we? In the 3-Tier scheme how many buildbots and test rigs are required vs. the work in trunk method? Sorry I've been a proponent of KISS for quite awhile. One thing I like about SVN is that it discourages branching to necessary times while git encourages branching for a whim. These are my opinions, it is the project's choice. Regards, Dave > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui >
