[asterisk-dev] git migration update

Nir Simionovich nir.simionovich at gmail.com
Tue Dec 23 01:24:03 CST 2014

+1 from me as well.

We use the methodology of using personalized repos for projects and it
works really well. We use either GitHub
or BitBucket, depending on the project - but both work equally well.

I'm confident that Atlassian will be happy to show their support by
contributing a Stash license to the project,
and you'll get the same functionality of BitBucket on a dedicated server -
if you don't want to host the project

On Tue, Dec 23, 2014 at 1:34 AM, Russell Bryant <russell at russellbryant.net>

> On Mon, Dec 22, 2014 at 3:08 PM, George Joseph <
> george.joseph at fairview5.com> wrote:
>> On Mon, Dec 22, 2014 at 12:03 PM, Samuel Galarneau <sgalarneau at digium.com
>> > wrote:
>>> 2 - we have a few options as far as team branches go. We could configure
>>> user branches using refs/heads/team/${username}/* permissions in Gerrit to
>>> allow users to create branches. This would prohibit other users from
>>> pushing to a user branch, but they would still be visible. This would most
>>> likely involve reproducing some sort of automerge/autorebase process. The
>>> other option is to use github as another remote for team branches, with a
>>> remote pointing to Gerrit for code reviews. Is there a preference between
>>> these two approaches, or perhaps a better setup we could follow?
>> I don't think there's any need for you to host users' repos any more.
>> It may have made sense for SVN but I don't think it does for GIT.  Let
>> users make their own arrangements be it GitHub or in my case, my own GIT
>> infrastructure.
> +1.  I don't think it makes sense with git.  github or whatever should
> work just fine for that purpose.
> --
> Russell Bryant
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20141223/5e011be2/attachment-0001.html>

More information about the asterisk-dev mailing list