12-18-2017 VF-C Weekly Meeting

Owned by Yan Yang
Last updated: Dec 18, 2017
1 min read

Attendees:

han yanan,maopeng,jinhua,Yan Yang,yunlong,Yufei Zhou, subhash

Agenda:

  1. Summarize the issues currently found

  2.  VF-C R2 Feature Planning& Implementation

  3. Other things

Minutes:

  1.  Summarize version update issues

  a. Artifacts version are not updated correctly in different branches. 

      pom modification should keep consistent with the version.properties update

     some components bumped the minor and patch version number, such as resmanagement components 

     Yan suggests team member check the version number update in both branch and make sure the artifacts have right version in nexus. 

  b. For the components with 1.0.1 and 1.0.2 version number delivered in Amsterdam release,  suggest to keep the consistent version number with 1.1.0.

      For these components, should bump the minor version and also drop the patch version to zero.

  c. Image version issue

      Dockerfile is the same in different  branches

      can't distinguish the version in different branches

       Need to find one component to be updated as an example and other components can follow

  d. JIRA bugs



  2.  Yan presents  VF-C R2 Feature Planning& Implementation

   a. Team familiar the requirements and calendar of Amsterdam maintenance release.

   b. Suggest team member create the jira bug with high or highest level and describe the bug in detail as much as possible in jira. Who create bug JIRA should notify team the JIRA link.      



Action:

 1. Team member should check the version number update in both branch and make sure the artifacts have right version in nexus.

 2. Jinhua updates the Dockerfile and build image script for LCM components and notify team members to change other componnents.

 3. Maopeng resolves the JIRA bugs