Hi Pam,

Thanks for bringing this up.

I would tend to believe there is a good intention in fixing those type of 
defects but it is definitely not the right timing. Like me, you have certainly 
seen some behaviors where people sometimes don’t realize they have to focus on 
what is important today to make the Release reality.

My suggestion to you. As you are the PTL, you are in the driver seat for your 
project and thus as a community we trust your judgment. More specifically, I 
would recommend to “Abandon” such commit and use the Jira field “fixversion” 
and assign this to “Beijing Release” . It may be good to tag them as 
“scan-report” (or whatever tag that makes sense to you and the team), so later 
when this is the right time you can come back on this defect.

Hope this helps.
My 2 cents.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: DRAGOSH, PAMELA L (PAM) [mailto:[email protected]]
Sent: Thursday, October 12, 2017 6:07 AM
To: Gildas Lanilis <[email protected]>; [email protected]; 
[email protected]
Subject: [onap-tsc] [onap-release] Problem with people creating JIRA's for 
unnecessary fixes

Gildas and TSC,

Please help me. I have people that are going outside my scrum and creating 
“BUGS” for sonar major/minor fixes. None of these are critical or identified 
during integration testing. It is past code freeze and RC0 and these are 
disruptive to the process for releasing code.

I have asked them to stop over the past 2 weeks but today I have 3 new JIRA’s 
to deal with. We are trying to get our artifacts released to meet RC0 
guidelines. At this point I don’t know what to do except to bring in the 
involvement of the TSC to get this behavior stopped.

While I appreciate the help, it would have been better for this work to be done 
months ago and not post code freeze. I’m also not sure what brought on this 
sudden interest in fixing sonar major/minor issues throughout policy project. 
None of these people have spoken to myself about working on policy, much less 
added themselves as contributors to the project.

What guidance is there for this?

Thanks,

Pam Dragosh
ONAP Policy PTL
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc

Reply via email to