On 7/8/13 02:40 , EBo wrote: > On Jul 7 2013 11:02 PM, Sebastian Kuzminsky wrote: >> On 07/07/2013 09:34 PM, Jon Elson wrote: >>> ... In the past stuff I pushed to the v2.5_branch also got merged >>> after a day >>> or so to master, but this doesn't seem to have happened on these >>> changes. >>> Is there something more I need to do to get them to merge to master? >>> I'd like to make sure they get into any new releases. >> >> The merge from 2.5 into master is done manually, "whenever someone >> feels >> like it". You're welcome to do it, or ask someone else to do it, or >> just wait until someone else feels like doing it ;-) ... > > Is there anyone skilled enough, and willing, to take on the job of > managing the main repository? If Seb or Jon are willing, it would be > good to to give them at least the responsibility or telling everyone > what needs to be merged in (instead of waiting until some kind soul > steps up).
We all manage the master branch together. There's no need to explicitly assign this responsibility to anyone, it's a normal part of the development process. See the gitworkflows manpage, "Merging upwards" section. When you commit to an older stable branch, merging your bugfix up to master is part of the process. Not everyone is comfortable doing the merge operation, in which case waiting and letting someone else do it is totally acceptable. On the rare occasion that the merge is urgent, a simple request for help works well. I think there's no need for more structure or process in this particular situation. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
