Our pr tests aren't good enough for what you propose
Sent from my iPhone > On May 19, 2015, at 11:12 AM, Dave Goodell (dgoodell) <dgood...@cisco.com> > wrote: > >> On May 19, 2015, at 5:08 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> >> wrote: >> >>> On May 18, 2015, at 5:03 PM, Mark Santcroos <mark.santcr...@rutgers.edu> >>> wrote: >>> >>> What I didn't see in the doc, will you continue to work with two repo's or >>> will that change too? >>> (I found that confusing as a newcomer) >> >> Unfortunately, yes, we will keep 2 repos. Github doesn't let us have >> per-branch permissions -- having multiple repos is the only way to have >> strict control over who can push to release branches. Sad panda. >> >> If Github ever does enact per-branch permissions, we will happily squash >> back down to a single repo. > > The other way to solve this issue would be to stop treating the master as a > general dumping ground for potentially unstable code where anyone can just > push any time they want. If we switched to using PRs for (essentially) all > code that goes into master as well, then we wouldn't need two different sets > of permissions. > > Back in the SVN days it was nice to have a trunk where people could freely > check in work because there was no other good system for keeping track of > your own work or sharing it with others. But with Git we no longer have > those problems. I can easily organize multiple concurrent streams of private > development, avoid losing work, and share work with others, all without > committing to some centralized master branch. > > -Dave > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/05/17419.php
