JI, LUSHENG"
Date: Friday, August 4, 2017 at 1:43 AM
To: "onap-tsc@lists.onap.org"
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/ID
behalf of Gildas Lanilis
mailto:gildas.lani...@huawei.com>>
Date: Friday, August 4, 2017 at 6:43 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
Hi,
Thanks David for sharing your analysis +1. Big chunk of code shou
, LUSHENG ; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
All,
I wanted to second Lushe
lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
On Behalf Of Stephen Terrill
Sent: Friday, August 04, 2017 3:01 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
Thanks for sharing your perspective Lusheng, I think its important
JI, LUSHENG"
Date: Friday, August 4, 2017 at 1:43 AM
To: "onap-tsc@lists.onap.org"
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/I
.onap.org]
On Behalf Of Stephen Terrill
Sent: Friday, August 04, 2017 3:01 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
Thanks for sharing your perspective Lusheng, I think its important to get the
perspectives of the projects into t
-tsc@lists.onap.org
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
Dear TSC and ONAP community,
As I am reading through this thread, I can certainly appreciate David’s good
intention behind the suggestion. Perhaps this is a minority opinion here, but
as a PTL and
To: "onap-tsc@lists.onap.org"
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
Hi,
It great that David highlighted this need, just a few thoughts from my
perspective:
- I read that there is general agreement about going for upstream
first.
pproval first.
Best Regards,
Steve.
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
On Behalf Of GILBERT, MAZIN E (MAZIN E)
Sent: 03 August 2017 18:33
To: Yunxia Chen
Cc: eric.deb...@orange.com; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Enforcing an "Upstrea
search.att.com>>
Date: Thursday, August 3, 2017 at 8:31 AM
To: Eric Debeau mailto:eric.deb...@orange.com>>
Cc: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
I am ok if the integration team wants to take
behalf of "GILBERT, MAZIN E (MAZIN
E)"
Date: Thursday, August 3, 2017 at 8:31 AM
To: Eric Debeau
Cc: onap-tsc
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
I am ok if the integration team wants to take the task of defining best code
practic
I am ok if the integration team wants to take the task of defining best code
practices and guidelines on significant code insertion. I agree with Ash that
code that can not be reviewed should not be committed blindly. But we need to
form guidelines so we are all following the same practices. Eve
> *Alla Goldner*
>
> Open Network Division
> Amdocs Technology
>
>
>
>
> *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-
> boun...@lists.onap.org ] *On Behalf Of
> *Sauvageau,
> David
> *Sent:* Wednesday, August 02, 2017 7:37 PM
> *To:* onap-t
I also agree with Dhananjay => We spend too much effort on functional aspects
for R1. There is still some issues to setup a full ONAP platform on Vanilla
OpenStack.
+1
I wonder if we should have alternate releases. One for new functionality
followed by one to clean up technical debt follow
On Behalf Of Sauvageau, David
Sent: Wednesday, August 02, 2017 7:37 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
Hi TSC members,
I would like to bring to our attention one major opportunity for i
+1 for raising this topic
We should avoid 10k LOC patches because it is very complex to review and is not
aligned with an open source spirit.
I do not believe that we should create another subcommitte to handle such
issue. The integration project may be able to detect such behavior and alerts
@01D30C3A.26ED03A0]
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
On Behalf Of Sauvageau, David
Sent: Wednesday, August 02, 2017 7:37 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
Hi TSC members,
I wou
With all respect, I think this might be better characterized. I don't think
the alternative to the current practices is "upstream first". Likewise, I
don't think it makes any sense to develop something that doesn't yet exist
by first forming a project elsewhere, like on Github, just so we can then
t; Ranny.
>
>
>
>
>
> *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org] *On Behalf Of *Sauvageau, David
> *Sent:* Wednesday, August 2, 2017 9:37 AM
> *To:* onap-tsc@lists.onap.org
> *Subject:* [onap-tsc] Enforcing an "Upstream first" approach
David
You are raising a valid point and it relates to my previous note to the TSC
about monitoring and evaluating code quality. I suggested forming a
subcommittee to make a recommendation. This is vital for the success of ONAP.
Our first release includes a merger of open ecomp and open-o compo
ap-tsc] Enforcing an "Upstream first" approach to ONAP
Hi TSC members,
I would like to bring to our attention one major opportunity for improvement in
the behaviour currently adopted by some of our community members.
I am observing a big number of very large commits (10’s of thousands of lin
boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org] *On Behalf Of *Ed Warnicke
> *Sent:* Wednesday, August 02, 2017 10:42 PM
> *To:* Sauvageau, David
> *Cc:* onap-tsc@lists.onap.org
> *Subject:* Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
&
m: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
On Behalf Of Ed Warnicke
Sent: Wednesday, August 02, 2017 10:42 PM
To: Sauvageau, David
Cc: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP
+1 Upstream first is crucial.
Happy to
+1 Upstream first is crucial.
Happy to share sane strategies I've seen work in the past if folks are
interested.
Ed
On Wed, Aug 2, 2017 at 9:37 AM, Sauvageau, David
wrote:
> Hi TSC members,
>
> I would like to bring to our attention one major opportunity for
> improvement in the behaviour curr
Hi TSC members,
I would like to bring to our attention one major opportunity for improvement in
the behaviour currently adopted by some of our community members.
I am observing a big number of very large commits (10’s of thousands of lines
of code in a single commit) which to me is a symptom of
25 matches
Mail list logo
