Difference between revisions of "Archived-Hc2vpp/Release Plans/Release Plan 18.04"

From fd.io
Jump to: navigation, search
m (Expected Dependencies on Other Projects)
 
(2 intermediate revisions by one other user not shown)
Line 3: Line 3:
 
Relying on VPP's 18.04 release: https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.04  
 
Relying on VPP's 18.04 release: https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.04  
  
== Release Deliverables (Tentative) ==
+
== Release Deliverables ==
  
 
  <jira jql='project = HC2VPP AND fixVersion = 18.04 AND labels = wiki18.04 ORDER BY issuetype ASC, status DESC, priority DESC'></jira>
 
  <jira jql='project = HC2VPP AND fixVersion = 18.04 AND labels = wiki18.04 ORDER BY issuetype ASC, status DESC, priority DESC'></jira>
  
=== Bugfixes and various improvements ===
+
=== All improvements/Bug fixes ===
  
 
[https://jira.fd.io/browse/HC2VPP-289?jql=project%20%3D%20HC2VPP%20AND%20fixVersion%20%3D%2018.04%20ORDER%20BY%20issuetype%20ASC%2C%20status%20DESC%2C%20priority%20DESC view in JIRA]
 
[https://jira.fd.io/browse/HC2VPP-289?jql=project%20%3D%20HC2VPP%20AND%20fixVersion%20%3D%2018.04%20ORDER%20BY%20issuetype%20ASC%2C%20status%20DESC%2C%20priority%20DESC view in JIRA]
  
=== JVPP (Tentative) ===
+
=== JVPP ===
 
   
 
   
 
[https://jira.fd.io/issues/?jql=project%20%3D%20VPP%20AND%20fixVersion%20%3D%2018.04%20AND%20component%20%3D%20%22Java%20API%20binding%22%20ORDER%20BY%20issuetype%20ASC%2C%20status%20DESC%2C%20priority%20DESC view in JIRA]
 
[https://jira.fd.io/issues/?jql=project%20%3D%20VPP%20AND%20fixVersion%20%3D%2018.04%20AND%20component%20%3D%20%22Java%20API%20binding%22%20ORDER%20BY%20issuetype%20ASC%2C%20status%20DESC%2C%20priority%20DESC view in JIRA]
  
== Release Milestones (Tentative) ==
+
== Release Milestones ==
  
 
<!-- It is not uncommon for a project as part of its release process to have Milestones (M0, M1, M2, RC0, RC1) with corresponding events which occur at various milestones (API Freeze, Code Freeze, etc).  This is the place to list Milestones, their expected dates, and their expected events (whether process events, API Freeze, or noting a deliverable is coming in at a particular event. -->
 
<!-- It is not uncommon for a project as part of its release process to have Milestones (M0, M1, M2, RC0, RC1) with corresponding events which occur at various milestones (API Freeze, Code Freeze, etc).  This is the place to list Milestones, their expected dates, and their expected events (whether process events, API Freeze, or noting a deliverable is coming in at a particular event. -->
Line 31: Line 31:
 
| (F0+6) 2018-04-09
 
| (F0+6) 2018-04-09
 
| Code complete, pull first release throttle branch, only bug fixes accepted on throttle train. After pull: main branch reopens for new feature / risky commits. First artifacts posted.  
 
| Code complete, pull first release throttle branch, only bug fixes accepted on throttle train. After pull: main branch reopens for new feature / risky commits. First artifacts posted.  
|-
 
| RC2
 
| (RC1+7) 2018-04-16
 
| Second artifacts posted.
 
 
|-
 
|-
 
| Formal Release  
 
| Formal Release  

Latest revision as of 20:04, 17 August 2023

Introduction

Relying on VPP's 18.04 release: https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.04

Release Deliverables

 HC2VPP-312 copy-config support (1.18.04 extension) Done 
HC2VPP-313 Configuration examples using ncclient library Done
view in JIRA

All improvements/Bug fixes

view in JIRA

JVPP

view in JIRA

Release Milestones

Milestone Date Deliverables
F0 2018-04-03 APIs frozen. low-risk changes accepted on main branch.
RC1 (F0+6) 2018-04-09 Code complete, pull first release throttle branch, only bug fixes accepted on throttle train. After pull: main branch reopens for new feature / risky commits. First artifacts posted.
Formal Release (RC2+14) 2018-04-30 18.04 artifacts available

Expected Dependencies on Other Projects