Good morning Sylvain,
I do not recommend that we raise a ticket when we find a criteria is not met.
This methodology is a factor of scope creep like we have observed during the
Frankfurt release.
I strongly recommend that each requirement is originally tracked per project as
a jira ticket or wi
+1, separate REQ JIRA will help tracking.
Sylvain,
The logging changes will also need some discussion. In earlier release,
logging project put out very detailed standards for log file formats and
mandated four separate log files. For consolidation of logs, filebeat
mechanism was suggeste
+1 Dan - these should all be captured as Guilin Release Requirements REQ
JIRA's. Just like what was done in Frankfurt.
Pam
On 4/29/20, 10:08 AM, "onap-...@lists.onap.org on behalf of TIMONEY, DAN"
wrote:
*** Security Advisory: This Message Originated Outside of AT&T ***.
Reference ht
All,
Capturing these all on a wiki page would be helpful. However, my concern is
that, when the time comes for us to commit to M1 for Guilin, we PTLs need to
have a definitive list of what we're being asked to commit to so that there are
no missed expectations.
I was thinking that items like
I knew that if I say anything in this thread it will mean I'll have to
do some extra work xD
but OK, I may start putting sth together but after a while I think that
actually a page in read the docs like documentation team has (doc
developer guide) would be more suitable. Any thoughts?
On 29.
Well, yes it's a good idea!
As part of it comes from SECCOM, I propose someone who has the two hats to
initiate the writing, a.k.a you :-P
De : Krzysztof Opasiak [k.opas...@samsung.com]
Envoyé : mercredi 29 avril 2020 15:37
À : DESBUREAUX Sylvain TGI/OLN; T
Hi,
On 29.04.2020 15:11, sylvain.desbure...@orange.com wrote:
Hey Dan,
Nope I didn't create any stories.
What I can do (if possible) is to create one story per requirement (I
count roughly 15) and create a sub task per project (if possible in
project board).
That would add 15 tasks per proje
Hey Dan,
Nope I didn't create any stories.
What I can do (if possible) is to create one story per requirement (I count
roughly 15) and create a sub task per project (if possible in project board).
That would add 15 tasks per project (knowing that some will be irrelevant for
the project, like "c
Sylvain,
Thank you for the excellent summary, which was also explained quite well at
last week’s virtual face to face event.
One process question, though: are there already user stories created for these
items (perhaps SECCOM user stories)? I want to make sure we’re tracking these
requirement
