From: Stefan F. <ste...@we...> - 2013-10-23 11:08:29
|
Mike, thanks for reminding me that I forgot to highlight this: * If all developers follow this strategy the release manager does in fact NOTHING, except than a final fast-forward from the feature branch to the develop branch. No code will be changed. This task ould be done by any other developer who can write to the repo. * If any developer choose not to follow the strategy, the release manager has NO power to prevent him from doing so. There is no special connection or dependency to my person. It is more a service that I try to offer to ensure that all tests have been run, that nothing gets merged silently to develop etc. I will have no rights how things get implemented and I have no intention to claim them, except by the power of argument. If a developer feels that I take to long to merge things, he is still free to merge as soon as he prefers. There are no additional rights on the repo associated on the repo with that. Git allows any approach of releases, branching or forking strategy, so any developer is free to choose his own approach. However freedom comes with the price of potential chaos. I suggest some discipline in the beginning of Rails 2.x to avoid what happened in Rails 1.x: It is not pretty bad, but I could be better. And for this I have to blame myself as I did not provide a clear proposal that others were able to follow easily. Stefan On 10/23/2013 11:06 AM, Mike Bourke wrote: > The only thing that I can see wrong with this proposal is the question of > what happens if you get hit by a bus or something, Stefan. Not that I wish > you any ill, but some sort of contingancy should be built into the plan :) > > Mike Bourke > Campaign Mastery http://www.campaignmastery.com > Co-author, Assassin's Amulet http://www.legaciescampaignsetting.com > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |