ONAP Meetings and Zoom Bridge Policy
General Code Commit Rules
• Any commit has to have a jira ticket.
• You cannot merge your own commit; someone else has to review/merge it after R1 RC0 and forward.
• After RC0 until release, only patches fixing a blocker bug may be merged (based on regression/severity/testing/impact analysis) at release branch. No new functionality is permitted.
• After RC0 until release, no patches modifying an API is permitted unless an API Waiver has been submitted at release branch and approved from TSC.
For significant New Code
• Definition of significant new code: guideline as 10K+ LOC in single commit but it is up to the PTLs to decide
• For incubation projects*:
- PTLs need to ensure significant code commitments align with project approvals in that release.
- Before the commit, developer is required to send an email to that project’s maillist for the coming commit. This email will include jira ticket / epic, and other related design docs for community to better understand this commit.
* Note: Right now, (Aug. 10. 2017) all projects are incubation projects
...
| Info |
|---|
Many approved TSC policies are children of this page, however some may be more relevant to other sections of the wiki. As long as the page is tagged with "tsc-policies" it will show up on this list. Any approved policy page should have an approval date and link to the decision where appropriate. |
| Filter by label (Content by label) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|