> The concern would be that without CI you have very limited visibility into
> the impact of the patches pre-merge. The automation at fd.io does a *lot*
> for you…
Absolutely. For the hackathons CI was an order or two of magnitude too slow.
And we would be doing the testing there and then.
I d
Ole,
The concern would be that without CI you have very limited visibility into
the impact of the patches pre-merge. The automation at fd.io does a *lot*
for you...
Ed
On Wed, Nov 15, 2017 at 3:50 PM Jon Loeliger wrote:
> On Wed, Nov 15, 2017 at 4:17 PM, Dave Wallace
> wrote:
>
>> Folks,
>>
(dbarach)
> ; Keith Burns (krb) ; Florin Coras
> (fcoras) ; John Lo (loj) ; Luke, Chris
> ; Damjan Marion ; Neale
> Ranns (nranns) ; vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Discussion Topic: creating demo branches in
> git.fd.io/vpp
>
> Just as a data-point.
>
) ;
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Discussion Topic: creating demo branches in git.fd.io/vpp
Just as a data-point.
What we have done for IETF hackathons is to create a branch on github. E.g:
https://github.com/vpp-dev/vpp/tree/ietf100-nat
This allows us to do "high speed collabor
On Wed, Nov 15, 2017 at 4:17 PM, Dave Wallace wrote:
> Folks,
>
> Per the action item from this yesterday's VPP weekly meeting, I'm asking
> for opinions from the VPP community on allowing the creation of demo
> branches in the VPP git repo.
>
> ...
>
> Pro: Will allow utilization of LF infra to
Just as a data-point.
What we have done for IETF hackathons is to create a branch on github. E.g:
https://github.com/vpp-dev/vpp/tree/ietf100-nat
This allows us to do "high speed collaboration". Then cherry pick what has
value after the event.
Perhaps something similar could be done for "demos"?
I have a mild preference that we avoid creating demo branches in the master vpp
repo. When faced with similar requirements, I’ve added branch(es) to ephemeral
downstream mirrors.
I suppose one could destroy demo branches in the master vpp repo, but
“something could go wrong...”
Thoughts?
Than
